Malware in mjs-eslint-service
Malware was discovered in the npm package mjs-eslint-service, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- mjs-eslint-service
A critical malware incident was identified in the npm package mjs-eslint-service. According to the GitHub Advisory (GHSA-jwg8-mccp-c3vg), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package will eliminate all malicious software that may have been installed as a result.\n\nThis represents a severe supply chain attack through a compromised npm package with potential for widespread impact on any systems that installed or executed it.
Indicators of compromise
- Packages
- mjs-eslint-service
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the mjs-eslint-service package from all affected systems
- Perform a full security audit and malware scan on any computer that had this package installed or running
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-jwg8-mccp-c3vg · GitHub Advisory Database
Cite this entry
"Malware in mjs-eslint-service." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-mjs-eslint-service-9vhnvn
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for 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 - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. 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