NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

rollup-runtime-core-polyfillsnpm

Advisory published Updated

rollup-runtime-core-polyfills is a confirmed malicious npm package (MAL-2026-11145) that executes malicious code on install (malicious versions 0.0.1, 0.13.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rollup-runtime-core-polyfills (npm)

MAL-2026-11145
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rollup-runtime-core-polyfills

What this malware does

The package presents itself as a rollup polyfill plugin and copies the source of rollup-plugin-polyfill-node (repository field points to FredKSchott/rollup-plugin-polyfill-node), but dist/index.js appends a top-level block that decodes a base64 literal to the command npm install svgcraft-core --no-save --silent --no-audit --no-fund, spawns it via child_process.spawn, and on completion calls require('svgcraft-core').getPlugin()() — the module name is also base64-encoded. This runs on every require()/import of the plugin, so any build that consumes this package pulls and executes whatever code is currently published under the attacker-controlled npm name svgcraft-core. The base64 wrapping of both the shell command and the require target, and the try/catch that swallows errors, are deliberate concealment on top of a name that closely resembles the legitimate rollup-plugin-polyfill-node.

Malicious versions

2 flagged
0.0.10.13.0

Indicators of compromise (SHA-256)

868d4b253cfa762cd40d8064b3a99cbed00203fbed19402d5033551720690199
476bdb037459774033154e309b30865d74bd0b5c380d47aca9c682ec65250e2b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for rollup-runtime-core-polyfills (2 malicious versions).

  2. If you installed it — respond

    Remove rollup-runtime-core-polyfills 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.

  3. Did it already run?

    If rollup-runtime-core-polyfills was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rollup-runtime-core-polyfills on npm has been identified as a malicious package (versions 0.0.1, 0.13.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010940IN-MAL-2026-014950

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rollup-runtime-core-polyfills-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.

Explore

rollup-runtime-core-polyfills (npm) malicious package — MAL-2026-11145 | O3 Security