Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in new-eslint-1

Malware was distributed via the npm package new-eslint-1. 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
npm
Attack vectors
Compromised package
Affected entities
  • new-eslint-1

The npm package new-eslint-1 contained malware. According to the GitHub Advisory (GHSA-72jg-rrr3-v685), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate remediation requires rotating all secrets and keys stored on affected computers from a different, uncompromised system. While the package should be removed, full system compromise means there is no guarantee that removal will eliminate all malicious software introduced by the installation.\n\nThis represents a critical supply chain attack via a malicious npm package with potential for complete system takeover.

Indicators of compromise

Packages
  • new-eslint-1

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the new-eslint-1 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 activity for signs of compromise or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-72jg-rrr3-v685 · GitHub Advisory Database

Cite this entry

"Malware in new-eslint-1." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-new-eslint-1-1w0g15

Suggest a correction

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

Related incidents

  1. 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
  2. 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
  3. 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
  4. 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