Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

rollup-plugin-polyfill-routenpm

Malicious code in rollup-plugin-polyfill-route (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3009
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rollup-plugin-polyfill-route

What this malware does

The package rollup-plugin-polyfill-route was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

47d00a54e90381fb52cc03bff987850baed2f3317a8ed939503b19bba0816b07
ae32c5ba788989f856ede10fa991e6dafa8d9263b0f5fc7384c69fba97e41d4a

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rollup-plugin-polyfill-route (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rollup-plugin-polyfill-route across your stack and pipelines.

  2. If you installed it — respond

    Remove rollup-plugin-polyfill-route 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-plugin-polyfill-route 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.

  4. How O3 protects you

    O3 blocks rollup-plugin-polyfill-route 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

No. rollup-plugin-polyfill-route on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9f4f-7957-69m9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rollup-plugin-polyfill-route-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.

rollup-plugin-polyfill-route (npm) malicious package — MAL-2026-3009 | O3 Security