Malware in eslint-publish-release
Malware was discovered in the npm package eslint-publish-release, resulting in full system compromise for any computer with the package installed or running. The package has been removed from distribution.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- eslint-publish-release
A malicious version of the npm package eslint-publish-release was identified and published to the npm registry. The package contained malware that could fully compromise any system on which it was installed or executed.\n\nAccording to the GitHub Advisory (GHSA-rqq3-8xp4-pvcq), 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, uncompromised system.\n\nWhile 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 alone will remove all malicious software resulting from the installation.\n\nThe incident was disclosed on August 18, 2026.
Indicators of compromise
- Packages
- eslint-publish-release
Remediation
- Immediately remove the eslint-publish-release package from all systems
- Rotate all secrets, API keys, and credentials stored on affected computers from a different, uncompromised system
- Perform a full security audit and malware scan of any system that had the package installed
- Review system logs and access logs for any unauthorized activity during the period the package was installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-rqq3-8xp4-pvcq · GitHub Advisory Database
Cite this entry
"Malware in eslint-publish-release." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-eslint-publish-release-7x96ig
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