rollup-plugin-polyfill-handler (npm) · Malicious Code
Affects rollup-plugin-polyfill-handlerSource GCVE Database
Malicious package : remove rollup-plugin-polyfill-handler and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 15:56 UTC
Malicious package
Published to npm · OSV MAL-2026-6826
What to do
Remove rollup-plugin-polyfill-handler from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmrollup-plugin-polyfill-handler | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8fcd05581537eece4993579cb664215a82b87dad2bdb03cae7ba998ba092a79d) 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. ## Source: ghsa-malware (eb53d850b987c8153dfa2ccba3634b4d653dbd66c8ed73198270232aa7562066) 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.