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

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)

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

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

8 flagged
0.13.40.13.50.13.60.13.70.13.80.13.90.14.00.14.1

Indicators of compromise (SHA-256)

69da81410d062733108728b42feb333d2f561f811a9c671664150cd026b12221
96f2a7710da85018d31f24bd4bfc5d10b25b439bc37b81eca966f761fab0c2e1
f89a5205cfb702df5a1481b6a3eadb64da36c695b13b42686a87b0f17035a46d
2dfdfbd2fc737f9d78ec40aac8b7020866cb0ef0e7e14b2d95aa174ea0ec5818
32e7813eae65ec25803d2163fbfcf3c05901e7197025d5ebc54a688d19e726cd
9b4d6b267c6acf02bfba1366c8d1fe3e3285f2fd492a34d2c499e33d7d2efcff
391335b48005ba6841c9f57fb0940155334d0259010ce46714da685a77c67b29
b90a0703bd52c4c4c8d51488944855cb03be1a1e1c6b769d04135ea6cc3dec43
bfe3556b46f99844468a8da34661086b69d11872929c010dd47e713d03d9996b

Detection & response playbook

Typosquat
  1. Find 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.

  2. 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.

  3. 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.

  4. 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

No. rollup-packages-polyfill-core on npm has been identified as a malicious package (versions 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.13.8, 0.13.9, 0.14.0, 0.14.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009674IN-MAL-2026-009671IN-MAL-2026-010882IN-MAL-2026-014921IN-MAL-2026-014918GHSA-vw6c-rv4h-v5pwIN-MAL-2026-018548IN-MAL-2026-018551IN-MAL-2026-018546

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.

Explore