Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in ecto-logger

Malware discovered in the npm package ecto-logger. Systems with this package installed or running are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with ecto-logger installed or running
Ecosystems
Attack vectors
Affected entities
  • ecto-loggernpm package

The npm package ecto-logger has been identified as containing malware. According to the GitHub advisory (GHSA-6224-2ghr-p5cq), 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, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.

Indicators of compromise

Packages
  • ecto-logger

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the ecto-logger package from all affected systems
  • Conduct a full security audit of any system that had ecto-logger installed
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-6224-2ghr-p5cq · GitHub Advisory Database

Cite this entry

"Malware in ecto-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 30, 2026; last updated July 30, 2026. https://supplychainattack.org/incident/malware-in-ecto-logger-139wsv

Suggest a correction

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

  1. containedcritical

    Malware in spectral-wraith

    Malware was discovered in the npm package spectral-wraith. 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
  2. activecritical

    Malware in @spectraltest/loglevel

    Malware discovered in the npm package @spectraltest/loglevel. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in wastu

    The npm package wastu was found to contain malware that grants full system compromise to attackers. Any system with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different computer.

    npmCompromised package
  4. resolvedcritical

    Malware in ag-grid-boost

    Malware was discovered in the npm package ag-grid-boost. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package