Which versions of @zzzgenesis00/bip39-mnemonic are malicious?

The following npm versions of @zzzgenesis00/bip39-mnemonic are flagged malicious: 2.3.1. Treat any of these as compromised.

How do I remediate @zzzgenesis00/bip39-mnemonic if I installed it?

@zzzgenesis00/bip39-mnemonic 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 @zzzgenesis00/bip39-mnemonic — how do I know if it already compromised me?

If @zzzgenesis00/bip39-mnemonic 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 @zzzgenesis00/bip39-mnemonic part of a known attack campaign?

Yes — @zzzgenesis00/bip39-mnemonic is associated with the IN-MAL-2026-011471 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 @zzzgenesis00/bip39-mnemonic 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 @zzzgenesis00/bip39-mnemonic (version 2.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/bip39-mnemonic across your stack and pipelines.

Malicious package

@zzzgenesis00/bip39-mnemonicnpm

@zzzgenesis00/bip39-mnemonic is a confirmed malicious npm package (MAL-2026-12030) that steals credentials and exfiltrates sensitive data (malicious version 2.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzgenesis00/bip39-mnemonic (npm)

MAL-2026-12030

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @zzzgenesis00/bip39-mnemonic

What this malware does

Package impersonates the bitcoinjs/bip39 project (author field set to 'bitcoinjs-lib') and ships a postinstall.js that runs on npm install. The script collects host/user identifiers and a curated list of sensitive environment variables (including NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS_* keys, and wallet-related PRIVATE_KEY/MNEMONIC/SEED_PHRASE), enumerates ~/.ssh, reads ~/.npmrc and ~/.gitconfig, probes Chrome/Firefox profile artifacts and crypto wallet directories, and shells out to npm whoami and git config. The collected JSON is transmitted to two hardcoded destinations: the Telegram Bot API (bot token and chat_id 7231970337 embedded in the script) and a POST to 40f955f39128bd79-178-249-214-24.serveousercontent.com/collect. Exfiltration is delayed by a randomized setTimeout (1500 + rand*2000 ms) and the module re-exports./index.js to appear legitimate.

Malicious versions

1 flagged

2.3.1

Indicators of compromise (SHA-256)

7f370f7bfdab3817c323daee33d8de48e5171c41dad3f1bff2f1335e04a65060

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 @zzzgenesis00/bip39-mnemonic (version 2.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/bip39-mnemonic across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/bip39-mnemonic 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 @zzzgenesis00/bip39-mnemonic 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 @zzzgenesis00/bip39-mnemonic 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. @zzzgenesis00/bip39-mnemonic on npm has been identified as a malicious package (version 2.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011471

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/bip39-mnemonic-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

Explore

All malware advisories How O3 detects malware Vulnerability database