rollup-plugin-polyfill-holdnpm
rollup-plugin-polyfill-hold is a confirmed malicious npm package (MAL-2026-11479) that executes malicious code on install (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rollup-plugin-polyfill-hold (npm)
What this malware does
The package presents itself as a rollup plugin / CDN icon-asset fetcher but its exported getPlugin, setPlugin, and getPluginExten functions issue HTTPS requests to a hardcoded endpoint at rest-icon-handler.store/icons/103 and /icons/389 and pass the JSON-parsed response body to eval(), giving the endpoint owner arbitrary JavaScript execution in the caller's Node process. The destination URL is assembled from split constants (protocol/separator/subdomain/domain/path) rather than appearing as a single string, while a decoy setDefaultModule references legitimate CDN providers (cloudflare/fastly/akamai) that are never contacted by the eval path. getPlugin additionally schedules getPluginExten via setTimeout so the fetch-and-eval recurs. The eval-of-remote-content behavior is not disclosed by the package's advertised purpose and the endpoint is unrelated to any documented CDN.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rollup-plugin-polyfill-hold (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rollup-plugin-polyfill-hold across your stack and pipelines.
If you installed it — respond
Remove rollup-plugin-polyfill-hold 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.
Did it already run?
If rollup-plugin-polyfill-hold 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-hold 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-hold-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.