Malicious code in rollup-packages-polyfill-core (npm)
The npm package 'rollup-packages-polyfill-core' contains malicious code that dynamically installs and executes a secondary malicious module named 'vectormark'. This package is a typosquat of the legitimate 'rollup-plugin-polyfill-node' and hides its malicious behavior by encoding commands and module names in base64. Installing or running this package can lead to full system compromise, requiring immediate secret and key rotation and package removal.
AI Analysis
Technical Summary
The 'rollup-packages-polyfill-core' npm package, specifically versions 0.13.7 and 0.13.8, contains malicious code that, upon requiring its main entry point, decodes and executes a base64-encoded shell command to install an unpinned secondary malicious package 'vectormark' without saving it to the consumer's lockfile. It then dynamically requires and executes this second-stage package, enabling arbitrary code execution. The package name is a typosquat of the legitimate 'rollup-plugin-polyfill-node', and the malicious commands are obfuscated using base64 encoding to evade static analysis.
Potential Impact
Any system with this package installed or running should be considered fully compromised. The attacker gains arbitrary code execution capabilities, potentially leading to complete system takeover. All secrets and keys on the affected system should be considered exposed and must be rotated immediately from a different, trusted system. Removing the package alone may not fully remediate the compromise due to potential persistence mechanisms.
Mitigation Recommendations
Remove the 'rollup-packages-polyfill-core' package immediately. Rotate all secrets and keys stored on the affected system from a separate, secure environment. Because the system may be fully compromised, consider rebuilding the system or performing a thorough forensic analysis to ensure all malicious artifacts are removed. There is no official patch or fix; avoidance and removal are the primary mitigations.
Malicious code in rollup-packages-polyfill-core (npm)
Description
The npm package 'rollup-packages-polyfill-core' contains malicious code that dynamically installs and executes a secondary malicious module named 'vectormark'. This package is a typosquat of the legitimate 'rollup-plugin-polyfill-node' and hides its malicious behavior by encoding commands and module names in base64. Installing or running this package can lead to full system compromise, requiring immediate secret and key rotation and package removal.
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-packages-polyfill-core' npm package, specifically versions 0.13.7 and 0.13.8, contains malicious code that, upon requiring its main entry point, decodes and executes a base64-encoded shell command to install an unpinned secondary malicious package 'vectormark' without saving it to the consumer's lockfile. It then dynamically requires and executes this second-stage package, enabling arbitrary code execution. The package name is a typosquat of the legitimate 'rollup-plugin-polyfill-node', and the malicious commands are obfuscated using base64 encoding to evade static analysis.
Potential Impact
Any system with this package installed or running should be considered fully compromised. The attacker gains arbitrary code execution capabilities, potentially leading to complete system takeover. All secrets and keys on the affected system should be considered exposed and must be rotated immediately from a different, trusted system. Removing the package alone may not fully remediate the compromise due to potential persistence mechanisms.
Mitigation Recommendations
Remove the 'rollup-packages-polyfill-core' package immediately. Rotate all secrets and keys stored on the affected system from a separate, secure environment. Because the system may be fully compromised, consider rebuilding the system or performing a thorough forensic analysis to ensure all malicious artifacts are removed. There is no official patch or fix; avoidance and removal are the primary mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10160
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a520ecc68715ace438f63fb
Added to database: 07/11/2026, 09:37:16 UTC
Last enriched: 09/12/2026, 18:47:32 UTC
Last updated: 09/12/2026, 18:47:32 UTC
Views: 111
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.
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.