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

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)

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

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

10 flagged
0.13.10.13.20.13.30.13.40.13.50.13.60.13.70.13.80.13.90.14.0

Indicators of compromise (SHA-256)

e1923adcd8dc53c5f68d2b6f1ef453f5dc52a71fcb2b9e9db502d308e5ef4311
90dc8536f81ef2ffbd391877bbe1eefbefc900081ef6eaa9848548177c233167
ebd136cb340adff0341c7b4f86b99d7c026ec67693d1d812559e0a56b64698ad
f21236e6de3a458e6dff10d509699f19731342b2b09affbbab93d1856328088e
86dd829b4d8f5036fa5ebd80007b813641508e5ba5fc0587e57308a3bbc62044
09e58d4bb25c5fe550e1ed3678541063c2480a5c8d9eb362f61b98cec35d0246
291dbf30d85584754c7efb24487c290a0aad9bfa57cde5ac4bb2e83928bba08a
5aa3e3aafa0e2cbe34fad2b6335ebcf6e80098d538000cb75137984846a8493b
6fdc8745ac118b8ce3f1767a9340d9da8b8a42f399d379a17751591133554381
bfc05640e218001f7f12a2e315094bbb69953e83af3426a261d568918587fd25
f0aa74642fe4bc310bea8b7613a56b7430f938cf2d1ccd1f82f5faffc70f053e

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

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

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

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

No. rollup-runtime-polyfill-core on npm has been identified as a malicious package (versions 0.13.1, 0.13.2, 0.13.3, 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.13.8, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007416IN-MAL-2026-009670IN-MAL-2026-009672IN-MAL-2026-009673GHSA-cx5m-r6wc-pp56IN-MAL-2026-018542IN-MAL-2026-018544IN-MAL-2026-018545IN-MAL-2026-018547IN-MAL-2026-018543IN-MAL-2026-018549

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.

Explore

rollup-runtime-polyfill-core (npm) malicious package — MAL-2026-6372 | O3 Security