Malware in @servicetitan/log-service
Malware was discovered in the npm package @servicetitan/log-service. 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
- @servicetitan/log-service
A critical malware incident was identified in the npm package @servicetitan/log-service. According to the GitHub Advisory (GHSA-g5j5-mfrp-8mh8), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated 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 compromise.\n\nThis represents a severe supply chain attack through a compromised npm package with potential for complete system compromise.
Indicators of compromise
- Packages
- @servicetitan/log-service
Remediation
- Immediately isolate any system that has @servicetitan/log-service installed or running
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @servicetitan/log-service package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if complete compromise is suspected
Sources
- GitHub Advisory GHSA-g5j5-mfrp-8mh8 · GitHub Advisory Database
Cite this entry
"Malware in @servicetitan/log-service." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-servicetitan-log-service-1b2rhg
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 @servicetitan/table
Malware was discovered in the npm package @servicetitan/table. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate, unaffected computer.
npmCompromised package - containedcritical
Malware in @servicetitan/standalone-root
Malware was discovered in the npm package @servicetitan/standalone-root, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
npmCompromised package - containedcritical
Malware in @servicetitan/anvil2-mcp
Malware was discovered in the npm package @servicetitan/anvil2-mcp. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in @servicetitan/docs-uikit
Malware was discovered in the npm package @servicetitan/docs-uikit. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
npmCompromised package