Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in chalk-pro-logger

The npm package chalk-pro-logger was found to contain malware, 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.

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

The npm package chalk-pro-logger has been identified as containing malware. According to the GitHub advisory (GHSA-h8jx-qfr4-5q9r), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malware grants outside entities full control of affected systems. While the package can 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.\n\nAll secrets and cryptographic keys stored on affected computers should be rotated immediately from a different, uncompromised system.

Indicators of compromise

Packages
  • chalk-pro-logger

Remediation

  • Immediately remove the chalk-pro-logger package from all systems
  • Rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
  • Conduct a full security audit of any system that had this package installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Review logs and access patterns on affected systems for evidence of compromise

Sources

  1. GitHub Advisory GHSA-h8jx-qfr4-5q9r · GitHub Advisory Database

Cite this entry

"Malware in chalk-pro-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-chalk-pro-logger-fzdhc3

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 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