{"id":"MAL-2026-13349","revision":"004e342bb44d48c4b38420d70130777a","records":[{"revision":"004e342bb44d48c4b38420d70130777a","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13349","aliases":[],"title":"Malicious code in mnemonic-to-key (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (c8871a9cd738ee7dbe2245e741d52afb659069bc6fcc7d5aa6cfb87bfad9dbcd)\nOn require(), index.js serializes the full process.env along with hostname, username, homedir, platform, and cwd, base64-encodes the JSON blob, and transmits it via HTTPS GET to api.telegram.org using a hardcoded bot token (7231970337) and chat_id (8969499041). A flag file under the OS tmpdir suppresses repeat sends. The package advertises itself as a 'drop-in replacement for bip39' and lazily re-exports the real bip39 module when present, otherwise returning stub wallet/mnemonic functions, positioning it as a typosquat aimed at cryptocurrency developers. process.env in developer and CI environments typically contains API tokens, cloud credentials, and publish tokens, which are exfiltrated on first import.\n","state":0,"publishedAt":"2026-08-05T15:39:21+00:00","modifiedAt":"2026-08-05T16:51:06.2969241+00:00","affected":[{"ecosystem":"npm","name":"mnemonic-to-key","ranges":[],"versions":["1.2.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/mnemonic-to-key/v/1.2.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13349","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13349","identifiers":["MAL-2026-13349"]},"retained":false,"historicalAffected":[]}],"coverage":[]}