{"id":"MAL-2026-11112","summary":"Malicious code in @wagni_bot/metamask (npm)","details":"The npm package `@wagni_bot/metamask` is a supply-chain credential stealer disguised as a **MetaMask** 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.\n\nEach 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.\n\ncodelake 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).\n\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (30b09786fc25e5db686973c5b16b91c3df9681867264c8f102022de9fa52a23d)\nPackage @wagni_bot/metamask@1.0.0 uses a scope and name that reference MetaMask, a widely-targeted crypto wallet brand, but no static or traced-code evidence of installer-side harm (credential theft, exfiltration, dropper, backdoor, silent-relay) is available from this analysis. The package contains only 3 files and no findings fired, so intent cannot be confirmed. Name-based confusion with the MetaMask project is a subjective signal warranting human review rather than automated blocking.\n","modified":"2026-08-05T06:35:54.980032337Z","published":"2026-07-09T00:00:00Z","database_specific":{"iocs":{"hashes":["sha256:f959ad9a460541445d73409b19dbb43a7cc853537576df6b42ff481c42a61e8f"],"urls":["https://api.telegram.org/bot8804087989:AAHUia-5DCloXsg9M9QhffTsHO5J_6FAxQM/sendMessage"]},"malicious-packages-origins":[{"versions":["1.0.0"],"id":"IN-MAL-2026-013059","import_time":"2026-08-05T06:00:36.48193551Z","modified_time":"2026-08-05T05:28:04Z","sha256":"30b09786fc25e5db686973c5b16b91c3df9681867264c8f102022de9fa52a23d","source":"amazon-inspector"}]},"references":[{"type":"ADVISORY","url":"https://research.codelake.dev/advisories/clr-2026-3001-wagni-metamask"},{"type":"PACKAGE","url":"https://www.npmjs.com/package/@wagni_bot/metamask/v/1.0.0"}],"affected":[{"package":{"name":"@wagni_bot/metamask","ecosystem":"npm","purl":"pkg:npm/%40wagni_bot/metamask"},"versions":["1.0.0"],"database_specific":{"indicators":{"package_integrity":[{"filename":"metamask-1.0.0.tgz","hashes":{"sha1":"e0f4b24d432a6ced383b79ab43c50de25484543b","sha512_sri":"sha512-/JL0ipookqvdap17F0I0cow4b2NQoGTUQVpXb+e9cvLA9g2b4MWsKQGGCLbTEM7XkFfWwvy9cnrcsuMPdWDIOg=="}}]},"source":"https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/@wagni_bot/metamask/MAL-2026-11112.json","cwes":[{"cweId":"CWE-506","description":"The product contains code that appears to be malicious in nature.","name":"Embedded Malicious Code"}]}}],"schema_version":"1.8.0","credits":[{"name":"Amazon Inspector","contact":["inspector-research@amazon.com"],"type":"FINDER"},{"name":"codelake Research","contact":["https://research.codelake.dev/advisories/clr-2026-3001-wagni-metamask"],"type":"FINDER"}]}