Malicious code in rollup-packages-polyfill-core (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-10160
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2dfdfbd2fc737f9d78ec40aac8b7020866cb0ef0e7e14b2d95aa174ea0ec5818) 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`, `require`s 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. ## Source: ghsa-malware (9b4d6b267c6acf02bfba1366c8d1fe3e3285f2fd492a34d2c499e33d7d2efcff) 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.
- Source published
- 10 Jul 2026 16:56:40 UTC
- Source modified
- 24 Sep 2026 09:12:21 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.