NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dont-gonpm

Advisory published Updated

dont-go is a confirmed malicious npm package (MAL-2025-190957) that steals credentials and exfiltrates sensitive data (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dont-go (npm)

MAL-2025-190957
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dont-go

What this malware does

The package dont-go was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
1.1.2

Indicators of compromise (SHA-256)

c0c93e615c56bff106ee80602d26264bb4224ac1cf87e741889b716bc63681aa
ffcbe928d7ee027a099e62084462a380459f221c740f4c9532f368bc7f76d522
316e5842d0f3c071d7b0ad0a08323e0f416d646c344f18aad3cc09855a87fe13

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for dont-go (version 1.1.2).

  2. If you installed it — respond

    dont-go is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If dont-go was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dont-go on npm has been identified as a malicious package (version 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-84rh-wv6h-wp3f

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dont-go-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

dont-go (npm) malicious package — MAL-2025-190957 | O3 Security