Malware in babel-preset-lib-client
Malware was discovered in the npm package babel-preset-lib-client. 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-preset-lib-clientnpm package
A malicious version of the npm package babel-preset-lib-client was identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAccording to the GitHub Advisory (GHSA-wxh7-fh8g-5j3m), any computer with this package installed or running should be considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, unaffected computer.\n\nWhile removal of the package is advised, there is no guarantee that removing it will eliminate all malicious software that may have been installed as a result of the compromise. Full system remediation may be required.
Indicators of compromise
- Packages
- babel-preset-lib-client
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, unaffected computer
- Remove the babel-preset-lib-client package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Audit npm dependencies in all projects to identify and remove this package
Sources
- GitHub Advisory GHSA-wxh7-fh8g-5j3m · GitHub Advisory Database
Cite this entry
"Malware in babel-preset-lib-client." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 13, 2026; last updated July 13, 2026. https://supplychainattack.org/incident/malware-in-babel-preset-lib-client-19rxit
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package