Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in color-cli-log

The npm package color-cli-log contains malware that grants full control of affected systems. Any computer 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
  • color-cli-lognpm package

The npm package color-cli-log has been identified as containing malware. According to the GitHub Advisory (GHSA-57f7-j94v-w2hw), any computer that has 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
  • color-cli-log

Remediation

  • Immediately isolate any computer with color-cli-log installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the color-cli-log package from all affected systems
  • Perform a full security audit and malware scan of affected systems
  • Review system logs for any unauthorized access or activity
  • Consider full system reimaging if compromise is confirmed

Sources

  1. GitHub Advisory GHSA-57f7-j94v-w2hw · GitHub Advisory Database

Cite this entry

"Malware in color-cli-log." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-color-cli-log-1cpwo4

Suggest a correction

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

  1. activecritical

    Malware in express-firegate

    Malware discovered in the npm package express-firegate. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. activecritical

    Malware in express-deflect

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

    npmCompromised package
  3. containedcritical

    Malware in chai-spycore

    Malware was discovered in the npm package chai-spycore, affecting any computer with the package installed or running. The compromise is considered critical as it grants full system control to an outside entity.

    npmCompromised package
  4. containedcritical

    Malware in pino-utils

    The npm package pino-utils was compromised and distributed with malware. Any system with the package installed should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

    npmCompromised package