npx-test-ma980

Details

**Severity:** Critical

**Affected versions:** `= 1.0.1`

## 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.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/5f0495009882359c4fb90f43d4c686a809dd861a/osv/malicious/npm/npx-test-ma980/MAL-2026-16310.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/5f0495009882359c4fb90f43d4c686a809dd861a/osv/malicious/npm/npx-test-ma980/MAL-2026-16310.json
- https://www.npmjs.com/package/npx-test-ma980/v/1.0.1
- https://github.com/advisories/GHSA-9vj4-6r95-2p6w

Compromised versions (1)

• = 1.0.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.