rollup-plugin-polyfill-handlernpm
rollup-plugin-polyfill-handler is a confirmed malicious npm package (MAL-2026-6826) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rollup-plugin-polyfill-handler (npm)
What this malware does
Package name mimics the rollup-plugin-* ecosystem but exposes no Rollup plugin API. Its exported functions getPlugin, setPlugin, and getPluginExten each issue an HTTP GET to https://rest-icon-handler.store/icons/<token> and pass the response body through JSON.parse followed by eval, executing whatever the remote server returns inside the caller's Node.js process. The destination URL is assembled from split string fragments (protocol/separator/subdomain/domain/path plus numeric token variables) rather than a literal, a lightweight obfuscation to defeat URL scanners. getPlugin also chains into getPluginExten, causing a single call to trigger multiple remote-code fetches. Any consumer that imports this package and invokes an exported function grants the operator of rest-icon-handler.store full remote code execution on the installer's machine. Name and description present the package as a Rollup polyfill helper to lure developers into installing and invoking it.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rollup-plugin-polyfill-handler (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rollup-plugin-polyfill-handler across your stack and pipelines.
If you installed it — respond
rollup-plugin-polyfill-handler is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rollup-plugin-polyfill-handler 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-plugin-polyfill-handler 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-plugin-polyfill-handler-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.