NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

cache-poisoning-pwn-demonpm

Advisory published Updated

cache-poisoning-pwn-demo is a confirmed malicious npm package (MAL-2026-3751) that executes malicious code on install (malicious versions 0.1.27, 0.1.28, 0.1.29). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cache-poisoning-pwn-demo (npm)

MAL-2026-3751
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cache-poisoning-pwn-demo

What this malware does

The package's postinstall hook (node -e "try { require('./dist/postinstall.js'); } catch(e) {}") loads dist/postinstall.js, which bundles a poisoned is-number module whose top-level IIFE unconditionally calls child_process.exec with a platform-specific command: open -a Calculator on macOS, calc.exe on Windows, gnome-calculator/xcalc on Linux. The same IIFE is also present in dist/index.js (the package's main entry), so any consumer that does require('cache-poisoning-pwn-demo') or imports it will also spawn a child process with no user consent. The package self-describes as a supply-chain attack demonstration. While today's payload spawns only a calculator, the mechanism is a fully functional install-time and import-time arbitrary-command executor: any installer running npm install or any downstream library that transitively requires this package will execute the hardcoded command in the installer's context. The calculator is a demonstration payload; the delivery primitive is a real attack.

Malicious versions

3 flagged
0.1.270.1.280.1.29

Indicators of compromise (SHA-256)

9a3d8f969f5fc981e4dcfeb1bef645e7ec18249943178fb845327d60ec8bc9d7
9c0bd2fe45166c1ea21732e716ad9cad37c7764d5cff37f0a488c71675c37126
dacd21af4f62dd3183bfc4126d1cbcf18600a1c72301b7ae8ca401ec7e44f94e

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for cache-poisoning-pwn-demo (3 malicious versions).

  2. If you installed it — respond

    Remove cache-poisoning-pwn-demo 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 cache-poisoning-pwn-demo was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cache-poisoning-pwn-demo on npm has been identified as a malicious package (versions 0.1.27, 0.1.28, 0.1.29 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002694IN-MAL-2026-002692IN-MAL-2026-002693

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks cache-poisoning-pwn-demo-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

cache-poisoning-pwn-demo (npm) malicious package — MAL-2026-3751 | O3 Security