OpenSSF/OSV advisory MAL-2026-12119 confirms this npm version as malicious. 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...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @zzzgenesis00/bitcoinjs-wallet (npm)
Details
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.
Decision reason
OpenSSF Malicious Packages via OSV confirms @zzzgenesis00/bitcoinjs-wallet@5.4.2 as malicious (MAL-2026-12119): Malicious code in @zzzgenesis00/bitcoinjs-wallet (npm)