Malware in pretty-pino-logger
Malware was discovered in the npm package pretty-pino-logger. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- pretty-pino-loggernpm package
The npm package pretty-pino-logger has been identified as containing malware. According to the GitHub advisory (GHSA-9vrr-rpr8-7hfj), 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 package installation, given the potential for full system compromise.\n\nThis is a critical supply chain incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- pretty-pino-logger
Remediation
- Immediately isolate any system with pretty-pino-logger installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the pretty-pino-logger package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs and access logs for signs of unauthorized activity
- Consider full system reimaging if compromise is confirmed
- Notify all users and systems that may have been affected by the compromised package
Sources
- GitHub Advisory GHSA-9vrr-rpr8-7hfj · GitHub Advisory Database
Cite this entry
"Malware in pretty-pino-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-pretty-pino-logger-1uiakg
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