Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

npx-test-ma980npm

npx-test-ma980 is a confirmed malicious npm package (MAL-2026-16310) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in npx-test-ma980 (npm)

MAL-2026-16310
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall npx-test-ma980

What this malware does

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.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

adfd1e5f7cc282648da56cdf50ac9c3cb27d6165fa4a3f8f3625b4a0c2694be6

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npx-test-ma980 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npx-test-ma980 across your stack and pipelines.

  2. If you installed it — respond

    Remove npx-test-ma980 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If npx-test-ma980 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks npx-test-ma980 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. npx-test-ma980 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020206

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks npx-test-ma980-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

npx-test-ma980 (npm) malicious package — MAL-2026-16310 | O3 Security