{"id":"MAL-2026-16310","revision":"64e3ed01196d407d923a4fd40a05fc8b","records":[{"revision":"64e3ed01196d407d923a4fd40a05fc8b","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16310","aliases":[],"title":"Malicious code in npx-test-ma980 (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (adfd1e5f7cc282648da56cdf50ac9c3cb27d6165fa4a3f8f3625b4a0c2694be6)\npackage.json declares a `bin` entry whose key contains shell metacharacters and a chained command: `\"tool & calc.exe\": \"./run.js\"`. On Windows, npm's bin shim/symlink generation and later invocation via `npm install -g` or `npx` can interpret the `&` in the bin key as a command separator, causing `calc.exe` to execute as an unintended side effect of installing or linking the package. The shipped `run.js` is a trivial `console.log(\"hello\")` and `payload.json` is empty, so the crafted bin key is the entire attack surface — a proof-of-concept exploit of npm bin-name handling that yields arbitrary command execution on the installer's host.\n","state":0,"publishedAt":"2026-09-21T03:21:25+00:00","modifiedAt":"2026-09-21T03:30:16.5597615+00:00","affected":[{"ecosystem":"npm","name":"npx-test-ma980","ranges":[],"versions":["1.0.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/npx-test-ma980/v/1.0.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16310","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16310","identifiers":["MAL-2026-16310"]},"retained":false,"historicalAffected":[]}],"coverage":[]}