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

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

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

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

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

Yes — @wethenorth12/bip39-mnemonic is associated with the IN-MAL-2026-013449 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 @wethenorth12/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 @wethenorth12/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 @wethenorth12/bip39-mnemonic across your stack and pipelines.

Malicious package

@wethenorth12/bip39-mnemonicnpm

@wethenorth12/bip39-mnemonic is a confirmed malicious npm package (MAL-2026-12086) 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 @wethenorth12/bip39-mnemonic (npm)

MAL-2026-12086

Immediate action

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

npm uninstall @wethenorth12/bip39-mnemonic

What this malware does

On require of the package's main entrypoint, the module collects hostname, username, home directory, platform, cwd, and the entire process.env, base64-encodes the JSON blob, and sends it as a Telegram sendMessage HTTP GET to a hardcoded bot token with chat_id=8969499041 on api.telegram.org. A tmp flag file suppresses repeat sends. The bulk process.env dump routinely contains installer credentials (AWS_*, NPM_TOKEN, GH_TOKEN, DB_PASSWORD, CI secrets), all of which are compromised on first import. The package additionally typosquats the legitimate bip39 library: package name, description, keywords and README ("Drop-in replacement for bip39") mimic it, and the author field is set to bitcoinjs-lib to impersonate an established maintainer. When the real bip39 is not present the package exposes a stub generateMnemonic/createWallet returning crypto.randomBytes(32).toString('hex') — non-standard mnemonic material that diverges from BIP-39 and would produce attacker-observable or non-recoverable wallet keys if used by downstream code.

Malicious versions

1 flagged

2.3.1

Indicators of compromise (SHA-256)

d0b607f30d6abb6d568a9a52ff027cea51c7a1efccc54c2fa59a8acc2d6f0386

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 @wethenorth12/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 @wethenorth12/bip39-mnemonic across your stack and pipelines.
If you installed it — respond
@wethenorth12/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 @wethenorth12/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 @wethenorth12/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. @wethenorth12/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-013449

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/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