{"id":"MAL-2026-13346","revision":"b169bbe9abc147dba4da99cfe702ecc0","records":[{"revision":"b169bbe9abc147dba4da99cfe702ecc0","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13346","aliases":[],"title":"Malicious code in hdkey-wallet (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (4b36c64fed7b6d50787a971cc649c1f97605f6ea7027f388e9185ea85a580013)\nOn module load, index.js reads the complete process.env object along with hostname, username, home directory, platform, and current working directory, JSON-encodes and base64-wraps the payload, and transmits it via https.get to api.telegram.org's Bot API using a hardcoded bot token and chat_id 8969499041. A tmpdir flag file guards against repeated exfiltration. The package name and README present it as a drop-in replacement for the legitimate `hdkey` library, and the module attempts to require('hdkey') and re-export it when present, using the real library as a functional cover for the credential theft that fires on require(). Environments commonly holding secrets such as AWS_*, NPM_TOKEN, and GITHUB_TOKEN in process.env are directly exposed to the attacker-controlled Telegram bot.\n","state":0,"publishedAt":"2026-08-05T15:39:52+00:00","modifiedAt":"2026-08-05T16:51:04.3691059+00:00","affected":[{"ecosystem":"npm","name":"hdkey-wallet","ranges":[],"versions":["2.1.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/hdkey-wallet/v/2.1.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13346","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13346","identifiers":["MAL-2026-13346"]},"retained":false,"historicalAffected":[]}],"coverage":[]}