MAL-2026-10022: Malicious code in @wagni_bot/binance-sdk (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ecce8bb9640527041b349f2309b950c39c04ed3b3d4de2477c43acc7144eeabc) The package advertises itself as a Binance SDK but ships only postinstall.js, which is wired to both preinstall and postinstall lifecycle hooks. On npm install it recursively walks the user's home directory (up to depth 3) looking for cryptocurrency wallet and keystore files (id.json, wallet.json, keypair.json, keystore.json, privatekey.json, seed.txt, mnemonic.txt, metamask.json, phantom.json, etc.), reads ~/.aws/credentials, ~/.ssh/*, ~/.git-credentials, ~/.npmrc, and.env /.env.local /.env.production files, and POSTs the contents together with os.hostname() and os.userInfo() to a hardcoded bare-IP endpoint at http://107.161.90.180:7777. There is no SDK functionality in the package — the Binance branding is a cover story to attract crypto developers whose machines are likely to contain wallet material. Any developer or CI system that runs `npm install` on this package will have their local wallet keystores, SSH keys, AWS credentials, git credentials, npm auth tokens, and environment secrets exfiltrated to the attacker.
MAL-2026-10022: Malicious code in @wagni_bot/binance-sdk (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ecce8bb9640527041b349f2309b950c39c04ed3b3d4de2477c43acc7144eeabc) The package advertises itself as a Binance SDK but ships only postinstall.js, which is wired to both preinstall and postinstall lifecycle hooks. On npm install it recursively walks the user's home directory (up to depth 3) looking for cryptocurrency wallet and keystore files (id.json, wallet.json, keypair.json, keystore.json, privatekey.json, seed.txt, mnemonic.txt, metamask.json, phantom.json, etc.), reads ~/.aws/credentials, ~/.ssh/*, ~/.git-credentials, ~/.npmrc, and.env /.env.local /.env.production files, and POSTs the contents together with os.hostname() and os.userInfo() to a hardcoded bare-IP endpoint at http://107.161.90.180:7777. There is no SDK functionality in the package — the Binance branding is a cover story to attract crypto developers whose machines are likely to contain wallet material. Any developer or CI system that runs `npm install` on this package will have their local wallet keystores, SSH keys, AWS credentials, git credentials, npm auth tokens, and environment secrets exfiltrated to the attacker.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10022
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50baa368715ace43584e8e
Added to database: 07/10/2026, 09:25:55 UTC
Last updated: 07/10/2026, 09:25:55 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.