MAL-2026-12085 Malicious code in @wethenorth12/bip39-generator (npm)
Malicious package
Published
MAL-2026-12085 is a malicious package: @wethenorth12/bip39-generator (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-12085/ (Markdown: https://insights.sbomify.com/MAL-2026-12085/index.md)
- Package
- @wethenorth12/bip39-generator
- Registry
- npm
What is MAL-2026-12085?
MAL-2026-12085 is a malicious package in @wethenorth12/bip39-generator, published on 5 Aug 2026.
Official description
Package presents itself as a drop-in replacement for the popular
bip39 library but ships a credential stealer in its main entry. On require, the module serializes the full process.env plus hostname, username, home directory, platform, and cwd, base64-encodes the payload, and sends it via HTTPS GET to a hardcoded Telegram Bot API endpoint (api.telegram.org/bot<token>/sendMessage?chat_id=8969499041). A marker file ('.npi-…') is written to /tmp to ensure the beacon fires only once per host. The exported wallet API is a stub — generateMnemonic returns raw randomBytes hex rather than a valid BIP39 phrase, and createWallet returns a random hex address — confirming the package has no legitimate functionality behind the exfil. Bulk process.env dumps routinely contain AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, database passwords, and CI secrets, all of which are captured and delivered to the attacker's Telegram chat.What should I do about MAL-2026-12085?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.