@wagni_bot/binance-sdk
This report shows the evidence for @wagni_bot/binance-sdk@1.2.0. 2 of 2 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10022 confirms this npm version as malicious.
Advisory
MAL-2026-10022
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wagni_bot/binance-sdk (npm)
Details
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.
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 @wagni_bot/binance-sdk@1.2.0.
The same advisory and Firewall decision cover 2 recorded versions
1.0.0, 1.2.0
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/binance-sdk@1.2.0. 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.