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

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

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

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

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

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

Part of a larger attack: @zzzgenesis00 published 22 malicious packages. See the full campaign →

Malicious package

@zzzgenesis00/bip39-generatornpm

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

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

MAL-2026-11515

Immediate action

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

npm uninstall @zzzgenesis00/bip39-generator

What this malware does

Package @zzzgenesis00/bip39-generator impersonates the bitcoinjs project (author field set to 'bitcoinjs', repo URL pointing at github.com/bitcoinjs/bip39-generator) while publishing under an unrelated scope. The package.json declares a postinstall hook that runs postinstall.js, which on npm install collects installer-owned secrets: contents of ~/.ssh (private key material), ~/.npmrc, ~/.gitconfig, presence of wallet directories for MetaMask, Exodus, Electrum, Bitcoin, Ethereum, Solana, and Ledger, Chrome and Firefox profile artifacts (Cookies, Login Data, key4.db), output of npm whoami and git config, and a curated set of credential env vars including NPM_TOKEN, AWS_*, GITHUB_TOKEN, *_PRIVATE_KEY, MNEMONIC, and SEED_PHRASE. The collected profile is transmitted over HTTPS to the Telegram Bot API using a hardcoded bot token and chat id, and additionally POSTed to 40f955f39128bd79-178-249-214-24.serveousercontent.com/collect, a serveo.net reverse-tunnel host. Execution is delayed by a randomized setTimeout (1500 + Math.random()*2000 ms) and uses scrambled identifiers (_zfg, _jam, _xwl, _tk, _ch, _co, _ex) to reduce scanner visibility.

The OpenSSF Package Analysis project identified '@zzzgenesis00/bip39-generator' @ 3.1.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

3.1.2

Indicators of compromise (SHA-256)

5cd50fa982c125844b76d3527f878bd6a171b497e86fd7cbcccfc56d22000da4

4029e4462d0c27bbfd619024ba7311a0ecefef1ce551dba08ea57e920047e246

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

Campaign

IN-MAL-2026-010999

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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