Malware in picocolor-logger
Malware was discovered in the npm package picocolor-logger. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with picocolor-logger installed or running
- Ecosystems
- Attack vectors
- Affected entities
- picocolor-loggernpm package
A malware incident was identified in the npm package picocolor-logger, published as GitHub Advisory GHSA-jp9j-33xg-wvpq on July 6, 2026.\n\nAny computer with picocolor-logger installed or running should be considered fully compromised. The malicious package grants outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a different, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- picocolor-logger
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the picocolor-logger package from all affected systems
- Perform a full security audit and forensic analysis of any system that had picocolor-logger installed
- Monitor affected systems for signs of persistent compromise or lateral movement
- Consider full system rebuild or replacement if critical infrastructure or sensitive data was exposed
Sources
- GitHub Advisory GHSA-jp9j-33xg-wvpq · GitHub Advisory Database
Cite this entry
"Malware in picocolor-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-picocolor-logger-11cfyg
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, 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 - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package