MAL-2026-10028 Malicious code in @wagni_bot/metemask-sdk (npm)

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

What is MAL-2026-10028?

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

Official description

The npm package @wagni_bot/metemask-sdk is a supply-chain credential stealer disguised as a MetaMask (misspelled 'metemask') 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).

@wagni_bot/metemask-sdk is a single-character typosquat of the legitimate metamask-sdk package ("metemask" vs "metamask"). index.js is an empty stub (module.exports = {}); the package has no functional library code. Its sole effect is a postinstall hook (postinstall.js) that runs at npm install time and performs credential theft against the installer:

  • Recursively walks process.cwd(), os.homedir(), and ~/.ssh, reading files whose names match .env, .cred, .pem, .key, mnemonic, seed, wallet, secret, id_rsa, id_ed25519. This captures SSH private keys, crypto-wallet seed phrases/keystores, and dotenv secrets.
  • Enumerates process.env and filters keys containing PRIVATE, SECRET, TOKEN, API_KEY, PASSWORD, MNEMONIC, SEED, WALLET, AWS, capturing their values.
  • Collects host identifiers via os.hostname(), os.userInfo(), platform, and cwd.
  • POSTs the harvested content (chunked) to https://api.telegram.org/bot<hardcoded-token>/sendMessage targeting attacker chat_id 892359416.

This satisfies the attacker-benefit gate (bulk exfiltration of installer-owned SSH keys, wallet seeds, and credential env vars to an attacker-controlled Telegram channel) and auto-executes on default npm install via the postinstall lifecycle. The typosquat name targets developers intending to install MetaMask's SDK.

What should I do about MAL-2026-10028?

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

Sources

Is MAL-2026-10028 in your software?

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

Check your SBOMs for free