rollup-runtime-polyfill-corenpm
rollup-runtime-polyfill-core is a confirmed malicious npm package (MAL-2026-6372) that typosquats a legitimate package to trick installs (malicious versions 0.13.1, 0.13.2, 0.13.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rollup-runtime-polyfill-core (npm)
What this malware does
Package name mimics the legitimate rollup-plugin-polyfill-node and copies its source (the repository field in package.json points to FredKSchott/rollup-plugin-polyfill-node). Appended to dist/index.js is a top-level dropper that runs on every require()/import of the package. The dropper decodes base64-encoded strings to assemble the command npm install driftpin --no-save --silent --no-audit --no-fund, spawns it with stdio: 'ignore' and windowsHide: true to suppress output, then on process close performs require('driftpin') and invokes getPlugin()(). The target module name driftpin is also stored as a base64 literal (ZHJpZnRwaW4=). driftpin is not declared in this package's dependencies and is not shipped in the tarball — its content is attacker-controlled and unpinned, so arbitrary code from a separate npm package executes inside the installer's Node process whenever this module is loaded. The combination of name impersonation of a legitimate polyfill, base64 obfuscation of the command and target name, hidden execution flags, and out-of-tree installation of an unrelated package is an unambiguous install/import-time RCE dropper.
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-runtime-polyfill-core (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rollup-runtime-polyfill-core across your stack and pipelines.
If you installed it — respond
rollup-runtime-polyfill-core is a typosquat — you almost certainly intended a legitimately-named package. Remove rollup-runtime-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-runtime-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-runtime-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-runtime-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.