rollup-packages-polyfill-corenpm
rollup-packages-polyfill-core is a confirmed malicious npm package (MAL-2026-10160) that typosquats a legitimate package to trick installs (malicious versions 0.13.4, 0.13.5, 0.13.6…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rollup-packages-polyfill-core (npm)
What this malware does
On require of the main entry dist/index.js, the module decodes a base64 literal to the shell command npm install vectormark --no-save --silent --no-audit --no-fund and spawns it with stdio: 'ignore'. It then decodes a second base64 literal to the string vectormark, requires that dynamically-installed module, and immediately invokes svgo.getPlugin()(), executing arbitrary code from the second-stage package. The install target is unpinned and installed with --no-save, so the dropped code is not recorded in the consumer's lockfile. Both the shell command and the target module name are stored as base64 strings (Buffer.from(..., 'base64').toString('utf8')) to hide them from static review. The package name rollup-packages-polyfill-core typosquats the legitimate rollup-plugin-polyfill-node, whose repository it also declares.
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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rollup-packages-polyfill-core (8 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-polyfill-core across your stack and pipelines.
If you installed it — respond
rollup-packages-polyfill-core is a typosquat — you almost certainly intended a legitimately-named package. Remove rollup-packages-polyfill-core, 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-polyfill-core 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-polyfill-core 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-polyfill-core-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.