Malicious code in npx-test-ma980 (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-16310
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (adfd1e5f7cc282648da56cdf50ac9c3cb27d6165fa4a3f8f3625b4a0c2694be6) package.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.
- Source published
- 21 Sep 2026 03:21:25 UTC
- Source modified
- 21 Sep 2026 03:30:16 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.