Malware in libsignal-node-travatiger
Malware discovered in the npm package libsignal-node-travatiger. Systems with this package installed are 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
- libsignal-node-travatiger
A malicious npm package named libsignal-node-travatiger has been identified as containing malware. According to the GitHub Security Advisory (GHSA-j2x4-j4hc-mvcv), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from installation.\n\nThis represents a critical supply chain attack through a malicious npm package, likely targeting users of the legitimate Signal protocol library.
Indicators of compromise
- Packages
- libsignal-node-travatiger
Remediation
- Immediately remove the libsignal-node-travatiger package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Perform a full security audit and malware scan of affected systems
- Review system logs for unauthorized access or activity
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Monitor for any indicators of compromise or data exfiltration
Sources
- GitHub Advisory GHSA-j2x4-j4hc-mvcv · GitHub Advisory Database
Cite this entry
"Malware in libsignal-node-travatiger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-libsignal-node-travatiger-cedxia
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting