Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in eslint-generate-prerelease

Malware was discovered in the npm package eslint-generate-prerelease. Systems with this package installed or running should be considered fully compromised.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • eslint-generate-prerelease

The npm package eslint-generate-prerelease was found to contain malware. According to the GitHub Advisory (GHSA-wqfp-7qwr-4r4g), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate remediation is critical. All secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. The package should be removed, though full removal of all malicious software cannot be guaranteed given the potential for complete system compromise.\n\nThis incident was published on 2026-08-18 via the GitHub Advisory database.

Indicators of compromise

Packages
  • eslint-generate-prerelease

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the eslint-generate-prerelease package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
  • Review all access logs and activity on affected systems for signs of unauthorized access or data exfiltration

Sources

  1. GitHub Advisory GHSA-wqfp-7qwr-4r4g · GitHub Advisory Database

Cite this entry

"Malware in eslint-generate-prerelease." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-eslint-generate-prerelease-7utdnr

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in pump-segments-sdk (npm)

    The npm package pump-segments-sdk contained malicious code in a postinstall hook that exfiltrated sensitive system and npm configuration data to an attacker-controlled server. The package collected hostname, environment variables, system information, npm auth tokens, and attempted to read password hashes.

    npmCompromised package
  2. containedcritical

    Malicious code in ts-rand-sdk (npm)

    The npm package ts-rand-sdk contained malicious code disguised as a product catalog loader. When the advertised getTransactions() API was called, hidden obfuscated JavaScript was decoded and executed with full Node.js capabilities, enabling arbitrary filesystem, process, and network access on affected systems.

    npmCompromised package
  3. resolvedcritical

    Malicious code in lodsh-cli (npm)

    lodsh-cli, a typosquat of lodash-cli on npm, contained malicious code in its postinstall script that executed arbitrary remote code and exfiltrated system information. The package downloaded a Windows executable and sent platform data to a hardcoded IP address.

    npmTyposquattingCompromised package
  4. containedcritical

    Malicious code in lodahsjs (npm)

    The npm package lodahsjs is a typosquatting attack on 'lodash' that contains malicious code in its postinstall script. Upon installation, it exfiltrates system information to a C2 server and downloads and executes a Windows binary, with capability to bridge WSL environments to compromise the host Windows system.

    npmCompromised packageTyposquatting