Malware in pino-formatter
Malware discovered in the npm package pino-formatter. Systems with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with pino-formatter installed or running
- Ecosystems
- Attack vectors
- Affected entities
- pino-formatternpm package
A critical malware incident has been identified in the npm package pino-formatter. According to the GitHub advisory (GHSA-gg8p-hh3f-m2vx), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate rotation of all secrets and keys stored on affected computers, performed 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 compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system takeover.
Indicators of compromise
- Packages
- pino-formatter
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the pino-formatter package from all affected systems
- Audit system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected systems as potentially fully compromised and plan for forensic analysis or reimaging
- Check for any other suspicious packages or modifications on affected systems
- Monitor for any unauthorized access attempts using rotated credentials
Sources
- GitHub Advisory GHSA-gg8p-hh3f-m2vx · GitHub Advisory Database
Cite this entry
"Malware in pino-formatter." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-pino-formatter-1ra15v
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malware in ulebkit
The npm package ulebkit contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in celonix-otp-react
Malware discovered in the npm package celonix-otp-react. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in checkout-create-pos-order-am
Malware discovered in the npm package checkout-create-pos-order-am. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in chai-foundry
Malware was discovered in the npm package chai-foundry, affecting any computer with the package installed or running. The compromise grants full system control to an outside entity and requires immediate remediation including secret rotation and package removal.
npmCompromised package