Which versions of dont-go are malicious?

The following npm versions of dont-go are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate dont-go if I installed it?

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.

I already installed dont-go — how do I know if it already compromised me?

If dont-go was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is dont-go part of a known attack campaign?

Yes — dont-go is associated with the GHSA-84rh-wv6h-wp3f campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dont-go across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dont-go (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dont-go across your stack and pipelines.

Malicious package

dont-gonpm

Malicious code in dont-go (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dont-go (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dont-go across your stack and pipelines.
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.
Did it already run?
If dont-go was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dont-go before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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.

Malware detection Runtime egress monitoring