Highnpm8 affected versions

@validator-sdk/pubkey

@validator-sdk/pubkey has 8 versions on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls @validator-sdk/pubkey.

@validator-sdk/pubkey@1.0.8
@validator-sdk/pubkey@1.0.7
@validator-sdk/pubkey@1.0.6
@validator-sdk/pubkey@1.0.5
@validator-sdk/pubkey@1.0.4
@validator-sdk/pubkey@1.0.3
@validator-sdk/pubkey@1.0.2
@validator-sdk/pubkey@1.0.0

The incident that flagged it

High29 Apr 2026

DPRK "PromptMink" campaign uses AI agents to insert @validate-sdk/v2 dependency

ReversingLabs traced a DPRK Famous Chollima / UNC1069 campaign that began with @hash-validator/v2 in Sept 2025 and evolved through Feb 28, 2026 to insert @validate-sdk/v2 as the malicious dependency of benign-looking "bait" SDKs aimed at AI coding agents. One AI-authored commit pulled @solana-launchpad/sdk into a crypto trading repo. Phase 4 in March 2026 used Rust NAPI modules and 85MB Node SEA bundles to exfiltrate full source trees. 300+ malicious package versions across 60+ unique packages observed.

Versions named here: 1.0.0, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

@validator-sdk/pubkey is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If @validator-sdk/pubkey is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.