Malicious code in pino-pretty-logs (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (f7864fcfe92b62b2ddc003e696cbe02d18e0979f4336bff4cc9352f318b260fa) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The pino-pretty-logs npm package versions 1.1.0 and 2.0.0 have been identified as containing malicious code. Installation or execution of these versions results in a full system compromise, potentially allowing an attacker to access all stored secrets and keys. Due to the severity of the compromise, simply uninstalling the package is insufficient to ensure system integrity, as additional malicious software may persist. Immediate secret and key rotation from a secure environment is necessary to mitigate the risk.
Potential Impact
Systems with pino-pretty-logs versions 1.1.0 or 2.0.0 installed or running are considered fully compromised. Attackers may have gained full control over the affected computer, including access to all stored secrets and keys. This represents a total breach of system confidentiality and integrity.
Mitigation Recommendations
Remove the affected versions of the pino-pretty-logs package immediately. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Because full system compromise is possible, further forensic analysis and remediation may be required beyond package removal. No official patch or fix is currently available.
Malicious code in pino-pretty-logs (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (f7864fcfe92b62b2ddc003e696cbe02d18e0979f4336bff4cc9352f318b260fa) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The pino-pretty-logs npm package versions 1.1.0 and 2.0.0 have been identified as containing malicious code. Installation or execution of these versions results in a full system compromise, potentially allowing an attacker to access all stored secrets and keys. Due to the severity of the compromise, simply uninstalling the package is insufficient to ensure system integrity, as additional malicious software may persist. Immediate secret and key rotation from a secure environment is necessary to mitigate the risk.
Potential Impact
Systems with pino-pretty-logs versions 1.1.0 or 2.0.0 installed or running are considered fully compromised. Attackers may have gained full control over the affected computer, including access to all stored secrets and keys. This represents a total breach of system confidentiality and integrity.
Mitigation Recommendations
Remove the affected versions of the pino-pretty-logs package immediately. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Because full system compromise is possible, further forensic analysis and remediation may be required beyond package removal. No official patch or fix is currently available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6862
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-7cfh-3cj9-3fc3"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c342927e9c797195f9dbc
Added to database: 07/06/2026, 23:03:05 UTC
Last enriched: 07/07/2026, 00:08:33 UTC
Last updated: 07/24/2026, 21:39:15 UTC
Views: 23
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.