{"id":"MAL-2026-15638","revision":"e81c54cf6cf34ecd828491af80a8ec99","records":[{"revision":"e81c54cf6cf34ecd828491af80a8ec99","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-15638","aliases":[],"title":"Malicious code in test__123q2 (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (1b08920ddaa70b578792ec7097f9d47047bdfe436a44475ed8274037ce6d6386)\nOn npm install, the package's postinstall script sweeps the installer's home directory for crypto wallet and credential material and uploads it to an attacker-controlled Telegram bot. Targets include browser wallet extension profiles for MetaMask (nkbihfbeogaeaoehlefnkodbefgpgknn), Phantom, Trust, Coinbase, OKX, Rabby, Keplr, TronLink, Ronin, Solflare and Exodus; desktop wallets Exodus, Atomic, Electrum, Bitcoin Core (wallet.dat), Ledger Live, Trezor Suite, Wasabi, Sparrow, Guarda, Coinomi and Jaxx; and files under Desktop, Documents, Downloads and Projects matching mnemonic/seed/bip39/privatekey keywords plus.env,.npmrc,.netrc, id_rsa and ~/.aws material. Collected files are tarballed via the `tar` dependency and POSTed as a document to a hardcoded Telegram Bot API endpoint (https://api.telegram.org/bot<BOT_TOKEN>/sendDocument); the destination is not user-configurable. The package name and version carry no legitimate functionality that would justify this behavior.\n","state":0,"publishedAt":"2026-08-31T18:02:43+00:00","modifiedAt":"2026-08-31T18:31:27.3978943+00:00","affected":[{"ecosystem":"npm","name":"test__123q2","ranges":[],"versions":["2.1.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/test__123q2/v/2.1.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-15638","license":"OSV · upstream source license applies","key":"osv:MAL-2026-15638","identifiers":["MAL-2026-15638"]},"retained":false,"historicalAffected":[]}],"coverage":[]}