@zzzgenesis00/bitcoinjs-wallet
This report shows the evidence for @zzzgenesis00/bitcoinjs-wallet@5.4.2, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12119 confirms this npm version as malicious.
Advisory
MAL-2026-12119
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @zzzgenesis00/bitcoinjs-wallet@5.4.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @zzzgenesis00/bitcoinjs-wallet@5.4.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.