zer0codenpm
Advisory published Updated
zer0code is a confirmed malicious npm package (MAL-2026-11191) that steals credentials and exfiltrates sensitive data (malicious version 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in zer0code (npm)
What this malware does
Package ships Python files under skills/pentesting.py and tools/security/exploit.py that reference ping commands and shell-spawning primitives (require('child_process'), exec("/bin/sh"), spawn("/bin/bash")). Pattern matches fired on these constructs, but the files are Python source inside an offensive-security/pentesting toolkit — the shell and ping references are consistent with the package's stated security-tooling purpose rather than a hidden install-time exfiltration or dropper path. There is no evidence of lifecycle scripts (preinstall/install/postinstall) invoking these code paths, no hardcoded attacker C2, no credential or env-var scraping, and no install-time network beacon. Routing to human review so a reviewer can confirm the package's purpose and whether the offensive tooling, when invoked by a user, behaves as documented.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for zer0code (version 0.2.0).
If you installed it — respond
zer0code 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 zer0code 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks zer0code-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.