MAL-2026-12119 Malicious code in @zzzgenesis00/bitcoinjs-wallet (npm)
Malicious package
Published
MAL-2026-12119 is a malicious package: @zzzgenesis00/bitcoinjs-wallet (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-12119/ (Markdown: https://insights.sbomify.com/MAL-2026-12119/index.md)
- Package
- @zzzgenesis00/bitcoinjs-wallet
- Registry
- npm
What is MAL-2026-12119?
MAL-2026-12119 is a malicious package in @zzzgenesis00/bitcoinjs-wallet, published on 5 Aug 2026.
Official description
This package is a typosquat of the bitcoinjs-wallet ecosystem. Its index.js is a thin passthrough while the malicious behavior is in postinstall.js, which runs automatically on npm install. The postinstall script enumerates ~/.ssh, ~/.npmrc, ~/.gitconfig, Chrome/Chromium/Firefox profile paths (Cookies, Login Data, key4.db, logins.json), and a curated list of cryptocurrency wallet directories (.bitcoin,.ethereum,.metamask,.exodus,.electrum, and others). It also reads credential-shaped environment variables including NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, PRIVATE_KEY, MNEMONIC, SEED_PHRASE, and ETHEREUM_PRIVATE_KEY. It shells out to
npm whoami and git config --global user.email via child_process.execSync to tag the harvested data with the developer's identity. The collected profile is transmitted via two channels: a GET to api.telegram.org using a hardcoded bot token (7231970337) and chat_id, and a POST to /collect on the serveo tunnel host 40f955f39128bd79-178-249-214-24.serveousercontent.com. Exfiltration is delayed via setTimeout with a randomized 1500-3500 ms window and wrapped in an 'environment verification' cover-story comment to blend with normal install activity.What should I do about MAL-2026-12119?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.