Malware in @servicetitan/hammer-react
Malware was discovered in the npm package @servicetitan/hammer-react. The advisory indicates that any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @servicetitan/hammer-react
A critical malware incident was identified in the npm package @servicetitan/hammer-react. According to the GitHub advisory (GHSA-x4vx-m5pv-w23h), the package contains malicious code that grants outside entities full control of affected systems.\n\nThe advisory recommends that any computer with this package installed or running be treated as fully compromised. All secrets, keys, and credentials stored on affected systems should be rotated immediately from a different, uncompromised computer.\n\nWhile the package should be removed, the advisory notes that full system compromise may have occurred, meaning removal of the package alone may not eliminate all malicious software that was installed as a result of the initial compromise.\n\nUsers should treat this as a critical incident requiring immediate incident response procedures.
Indicators of compromise
- Packages
- @servicetitan/hammer-react
Remediation
- Immediately identify all systems with @servicetitan/hammer-react installed or running
- Isolate affected systems from the network if possible
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @servicetitan/hammer-react package from all affected systems
- Conduct a full forensic investigation of affected systems for additional malware or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Monitor for any indicators of compromise or unauthorized access using the rotated credentials
Sources
- GitHub Advisory GHSA-x4vx-m5pv-w23h · GitHub Advisory Database
Cite this entry
"Malware in @servicetitan/hammer-react." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-servicetitan-hammer-react-1l0tmj
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