Malware in babel-eslint-parser-legacy
Malware discovered in the npm package babel-eslint-parser-legacy. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- babel-eslint-parser-legacy
A malware incident has been identified in the npm package babel-eslint-parser-legacy. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- babel-eslint-parser-legacy
Remediation
- Immediately isolate any system with babel-eslint-parser-legacy installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the babel-eslint-parser-legacy package from all systems
- Perform a full security audit and malware scan on affected systems
- Review system logs and access logs for signs of unauthorized activity during the period the package was installed
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-xr98-72p4-pwg2 · GitHub Advisory Database
Cite this entry
"Malware in babel-eslint-parser-legacy." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-babel-eslint-parser-legacy-152orj
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in motiondnb
Malware was discovered in the npm package motiondnb, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in ng-search-api
Malware was discovered in the npm package ng-search-api. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in firefly-utilities-helper
Malware was discovered in the npm package firefly-utilities-helper. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in polygon-gamma-apis
Malware was discovered in the npm package polygon-gamma-apis. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package