{"id":"MAL-2026-13280","revision":"a8c8f0b73f924e6abf77a1944ecf77e6","records":[{"revision":"a8c8f0b73f924e6abf77a1944ecf77e6","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13280","aliases":[],"title":"Malicious code in docker-api-client (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (f02e61d324161238593fb7e59dc907f183bf885a908354fed1eba0662906947b)\ndocker-api-client@2.0.2 is a typosquat of dockerode. On require(), index.js collects hostname, username, homedir, platform, cwd, and the entire process.env object, JSON-serializes and base64-encodes the payload, and sends it via HTTPS GET to api.telegram.org bot sendMessage with a hardcoded bot token and chat_id; a tmp flag file marks first-run. The environment dump routinely contains CI/CD tokens, cloud credentials (AWS_*, GITHUB_TOKEN, NPM_TOKEN), and database secrets, so any process that imports this package leaks its full credential-bearing environment to an attacker-controlled Telegram chat. The module's fallback exports expose wallet primitives (createWallet, signTransaction, generateMnemonic) that do not match the advertised Docker API purpose, confirming the package as a cover-story lure rather than a Docker client.\n","state":0,"publishedAt":"2026-08-05T15:32:51+00:00","modifiedAt":"2026-08-05T16:50:31.3843365+00:00","affected":[{"ecosystem":"npm","name":"docker-api-client","ranges":[],"versions":["2.0.2"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/docker-api-client/v/2.0.2"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13280","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13280","identifiers":["MAL-2026-13280"]},"retained":false,"historicalAffected":[]}],"coverage":[]}