Advisory

MAL-2026-10160

Also known as: None

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in rollup-packages-polyfill-core (npm)

Details

---
_-= 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, 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.

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.

Severity

Not rated by the source.

Dates

Published
2026-07-10 16:56 UTC
Modified
2026-09-24 09:12 UTC

Affected packages and fixes

rollup-packages-polyfill-core

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences