rollup-packages-node-polyfills has 0 versions on the npm registry flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories. rollup-packages-node-polyfills was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.
If one is in your tree, treat the machine as compromised, not just out of date.
Version data comes from the public advisories cited on each incident page.
Check what you actually have installed with npm ls rollup-packages-node-polyfills.
13 new GHSA CWE-506 malware advisories in the 24h ending 2026-08-22. PyPI requests-crypt is the fourth variant of the 2026-08-reqcrypt HTTP-response exec() register; boto4 is a Telegram-bot-controlled miner + LAN worm. npm side: lumen-pages-community/@gfe/lx-watcher dep-confusion beacons, fuel-react env exfil, and a new JFrog/Lazarus rollup-family sibling.
Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
If rollup-packages-node-polyfills is in your tree, these are worth checking too. They were published by the same campaign.
Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.
It is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once. It runs in your browser and nothing is uploaded.