Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in eslint-plugin-totara

Malware was discovered in the npm package eslint-plugin-totara. Systems with this package installed are considered fully compromised and require immediate remediation.

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

A malware incident was identified in the npm package eslint-plugin-totara. According to the GitHub Advisory (GHSA-gvr8-64fv-6p2h), any computer with 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 removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis is a critical supply chain incident affecting the npm ecosystem through a compromised package vector.

Indicators of compromise

Packages
  • eslint-plugin-totara

Remediation

  • Immediately rotate all secrets and keys stored on affected computers from a different, uncompromised system
  • Remove the eslint-plugin-totara package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if compromise is suspected beyond the package itself

Sources

  1. GitHub Advisory GHSA-gvr8-64fv-6p2h · GitHub Advisory Database

Cite this entry

"Malware in eslint-plugin-totara." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-eslint-plugin-totara-18dh93

Suggest a correction

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

  1. activecritical

    Malware in @contentprod-authoring/block-manager

    Malware was discovered in the npm package @contentprod-authoring/block-manager. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malware in @webda-infra/search

    Malware was discovered in the npm package @webda-infra/search. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in @citi-icg-171632/citicms-repo-component

    The npm package @citi-icg-171632/citicms-repo-component contained malware that provided full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately.

    npmCompromised package
  4. activecritical

    Malware in @bscom/styling

    The npm package @bscom/styling contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package