Malware in rollup-runtime-polyfill-core
Malware discovered in the npm package rollup-runtime-polyfill-core. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- rollup-runtime-polyfill-core
A malware-laden version of the npm package rollup-runtime-polyfill-core has been identified and published to the npm registry. The package grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may persist even after package removal due to the level of system access it provides.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The package should be removed, though complete remediation may require additional forensic investigation and system hardening.
Indicators of compromise
- Packages
- rollup-runtime-polyfill-core
Remediation
- Immediately remove the rollup-runtime-polyfill-core package from all affected systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Conduct forensic analysis to identify any additional malicious software installed via this package
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Audit all systems that may have been compromised through this package for lateral movement
Sources
- GitHub Advisory GHSA-cx5m-r6wc-pp56 · GitHub Advisory Database
Cite this entry
"Malware in rollup-runtime-polyfill-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 21, 2026; last updated August 21, 2026. https://supplychainattack.org/incident/malware-in-rollup-runtime-polyfill-core-1rw4kl
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package