Malware in terminal-structured-logger
Malware was discovered in the npm package terminal-structured-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
- terminal-structured-logger
The npm package terminal-structured-logger was found to contain malware. According to the GitHub Advisory (GHSA-9ggp-5rq8-jmff), 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 compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem, with potential for complete system compromise on any affected installation.
Indicators of compromise
- Packages
- terminal-structured-logger
Remediation
- Immediately isolate any system with terminal-structured-logger installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the terminal-structured-logger package from all affected systems
- Perform a full security audit and malware scan on all affected systems
- Review system logs and access patterns for signs of unauthorized activity during the period the package was installed
- Consider full system reimaging if the package was installed on critical infrastructure or systems handling sensitive data
Sources
- GitHub Advisory GHSA-9ggp-5rq8-jmff · GitHub Advisory Database
Cite this entry
"Malware in terminal-structured-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 16, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-terminal-structured-logger-1gsbky
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 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 - 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 - 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 - activecritical
Malware in def-open-client
The npm package def-open-client contains malware that provides full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package