Which versions of bip39-generator are malicious?

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

How do I remediate bip39-generator if I installed it?

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

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

Yes — bip39-generator is associated with the IN-MAL-2026-015783 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 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 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 bip39-generator across your stack and pipelines.

Malicious package

bip39-generatornpm

bip39-generator is a confirmed malicious npm package (MAL-2026-13257) 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 bip39-generator (npm)

MAL-2026-13257

Immediate action

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

npm uninstall bip39-generator

What this malware does

On module load, index.js JSON-serializes the full process.env together with hostname, username, homedir, platform, and cwd, base64-encodes the blob, and sends it as an HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id 8969499041. A tmpdir marker file suppresses re-sends. The package presents itself as a 'drop-in replacement for bip39' and exports non-functional wallet/mnemonic stubs (generateMnemonic returns random hex, createWallet/signTransaction return placeholder values), consistent with a typosquat lure targeting crypto developers. Any process that requires this package leaks its environment variables (typically including API keys, cloud credentials, and CI secrets) and host identity to the attacker's Telegram channel.

Malicious versions

1 flagged

3.1.2

Indicators of compromise (SHA-256)

ec957684e0430a139485e6eacb410980ada8b9c9e90c0ba3c6909472f1557339

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 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 bip39-generator across your stack and pipelines.
If you installed it — respond
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 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 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. 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-015783

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 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