Malware in eslint-generate-release
Malware was discovered in the npm package eslint-generate-release. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from unaffected systems.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- eslint-generate-release
The npm package eslint-generate-release was found to contain malware. According to the GitHub Advisory (GHSA-3pw3-hc35-j73p), any computer with this package installed or running should be considered fully compromised.
The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, unaffected 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 removal of the package alone may not eliminate all malicious software that resulted from installation.
Users should treat any system that installed or ran this package as potentially containing persistent malware beyond the package itself.
Indicators of compromise
- Packages
- eslint-generate-release
Remediation
- Remove the eslint-generate-release package immediately from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis or rebuild affected systems
- Review access logs and audit trails for any unauthorized activity on affected systems
- Monitor for any persistence mechanisms or additional malware that may have been installed
Sources
- GitHub Advisory GHSA-3pw3-hc35-j73p · GitHub Advisory Database
Cite this entry
"Malware in eslint-generate-release." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-eslint-generate-release-wew5e5
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package