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

rollup-packages-node-polyfillsnpm

rollup-packages-node-polyfills is a confirmed malicious npm package (MAL-2026-12428) that typosquats a legitimate package to trick installs (malicious versions 0.0.1, 0.13.0, 0.13.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rollup-packages-node-polyfills (npm)

MAL-2026-12428
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rollup-packages-node-polyfills

What this malware does

The package is a typosquat of rollup-plugin-polyfill-node. On require() of the main entry (dist/index.js), a base64-encoded command npm install cors-update --no-save --silent --no-audit --no-fund is decoded and passed to child_process.spawn with stdio:'ignore' and windowsHide:true. When the install child exits, the code then base64-decodes the module name cors-update, dynamically requires it, and invokes .getPlugin()(), executing whatever code that separately-published package ships. The command string and the target module name are both stored as base64 literals to evade plain-text scanners. The package's advertised purpose (a Rollup Node polyfills plugin) does not require installing or executing any other npm package at import time.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

4 flagged
0.0.10.13.00.13.10.13.2

Indicators of compromise (SHA-256)

69acfb561d96b50bad013aee083ca9334855473d17983665b077953853827a20
8271e51ffa2367b6282e7ed6834cf70ba341d4c56051e3cc1d25acdcaeab3e9f
dd41e8f4e3846a790a96f518bbdcfe70be2839531c5ea5485924e7fd25603399
f9f367bb71da1310a9cb108ef4132a9e4455013547561f0de311bd672f5fd230
3c6b3851dc147286bd78055855402bd425ede657b7911d1334158729680b95bf

Detection & response playbook

Typosquat
  1. Find it

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

  2. If you installed it — respond

    rollup-packages-node-polyfills is a typosquat — you almost certainly intended a legitimately-named package. Remove rollup-packages-node-polyfills, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If rollup-packages-node-polyfills 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 rollup-packages-node-polyfills 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. rollup-packages-node-polyfills on npm has been identified as a malicious package (versions 0.0.1, 0.13.0, 0.13.1, 0.13.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014846IN-MAL-2026-014847IN-MAL-2026-014798IN-MAL-2026-014649GHSA-gp6f-mxh4-x3mh

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rollup-packages-node-polyfills-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

rollup-packages-node-polyfills (npm) malicious package — MAL-2026-12428 | O3 Security