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)
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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.
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.
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.
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
Campaign
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.