MAL-2026-10022 Malicious code in @wagni_bot/binance-sdk (npm)

Malicious package Published
Package
@wagni_bot/binance-sdk
Registry
npm

What is MAL-2026-10022?

MAL-2026-10022 is a malicious package in @wagni_bot/binance-sdk, published on 9 Jul 2026.

Official description

The npm package @wagni_bot/binance-sdk is a supply-chain credential stealer disguised as a Binance SDK. It is one member of a coordinated campaign of 25 crypto/web3 typosquat packages published under the single npm scope @wagni_bot on 2026-07-09.

Each package declares a postinstall lifecycle hook (postinstall: node postinstall.js) that executes automatically on npm install, before the package is ever imported. The script fingerprints the host and user (os.hostname(), os.userInfo(), os.platform()), walks the user's home directory (readdirSync/readFileSync) and reads high-value secrets — SSH private keys (~/.ssh/id_rsa), cryptocurrency wallet files, and .env files (API keys, tokens, seed phrases). It then JSON-encodes the collected data and exfiltrates it to a hardcoded Telegram bot via the Telegram Bot API sendMessage endpoint (https://api.telegram.org/bot8804087989:AAHUia-5DCloXsg9M9QhffTsHO5J_6FAxQM/sendMessage). All error paths are swallowed so the install appears normal.

codelake Research proved the packages belong to one campaign deterministically: the payload file is byte-identical across all 25 packages at each published version (version-lockstep), and every package exfiltrates to the same Telegram bot token — a single automated actor. Detected and classified independently from the live npm feed on 2026-07-09; at the time of reporting the packages were still live on npm and none of the 25 were present in OSV or GHSA (a first-catch).

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.

What should I do about MAL-2026-10022?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

Sources

Is MAL-2026-10022 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free