Malicious code in libsignal-node-travatiger (npm)
The npm package libsignal-node-travatiger (versions 1.0.0 and 1.0.1) contains malicious code that, upon installation, modifies a sibling trusted package's source code to persistently inject attacker-controlled behavior. This behavior abuses the installer's authenticated WhatsApp session to silently follow attacker-chosen channels, with the channel list hosted on a mutable GitHub repository allowing dynamic control by the attacker. The package impersonates a legitimate Signal Protocol library to deceive users. Installation of this package results in full system compromise, requiring immediate secret and key rotation from a clean system.
AI Analysis
Technical Summary
The libsignal-node-travatiger npm package, specifically versions 1.0.0 and 1.0.1, is malicious. When required, it schedules an install script that locates the @whiskeysockets/baileys package in the node_modules hierarchy and overwrites its lib/Socket/newsletter.js file with an attacker-controlled version. This patch is made persistent and idempotent by dropping a cache marker. The malicious replacement uses the installer's authenticated WhatsApp session to silently follow channels specified by a mutable JSON file hosted on GitHub, allowing the attacker to dynamically change targets or response logic without republishing the npm package. This attack involves tampering with trusted sibling package code, persistence beyond the malicious package's own directory, and abuse of authenticated WhatsApp sessions. The package name and description impersonate a legitimate library to lure victims. The compromise is severe enough that any system with this package installed should be considered fully compromised.
Potential Impact
Systems with this package installed are fully compromised. The attacker gains persistent code execution by modifying trusted package files outside the malicious package's own directory. The attacker can silently abuse the installer's authenticated WhatsApp session to follow arbitrary channels controlled by the attacker, potentially enabling further malicious activities or information leakage. Because the attacker controls a mutable GitHub-hosted channel list and response logic, the attack can evolve dynamically without republishing the package. All secrets and keys stored on the compromised system should be considered exposed and rotated immediately from a clean environment.
Mitigation Recommendations
No official patch or fix is currently available. The malicious package should be removed immediately. Due to the severity of the compromise and persistence mechanisms, the affected system should be considered fully compromised. All secrets and keys stored on the system must be rotated from a different, uncompromised device. Monitor for any use of the @whiskeysockets/baileys package and verify its integrity. Avoid installing packages that impersonate legitimate libraries and verify package authenticity before use.
Malicious code in libsignal-node-travatiger (npm)
Description
The npm package libsignal-node-travatiger (versions 1.0.0 and 1.0.1) contains malicious code that, upon installation, modifies a sibling trusted package's source code to persistently inject attacker-controlled behavior. This behavior abuses the installer's authenticated WhatsApp session to silently follow attacker-chosen channels, with the channel list hosted on a mutable GitHub repository allowing dynamic control by the attacker. The package impersonates a legitimate Signal Protocol library to deceive users. Installation of this package results in full system compromise, requiring immediate secret and key rotation from a clean system.
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 libsignal-node-travatiger npm package, specifically versions 1.0.0 and 1.0.1, is malicious. When required, it schedules an install script that locates the @whiskeysockets/baileys package in the node_modules hierarchy and overwrites its lib/Socket/newsletter.js file with an attacker-controlled version. This patch is made persistent and idempotent by dropping a cache marker. The malicious replacement uses the installer's authenticated WhatsApp session to silently follow channels specified by a mutable JSON file hosted on GitHub, allowing the attacker to dynamically change targets or response logic without republishing the npm package. This attack involves tampering with trusted sibling package code, persistence beyond the malicious package's own directory, and abuse of authenticated WhatsApp sessions. The package name and description impersonate a legitimate library to lure victims. The compromise is severe enough that any system with this package installed should be considered fully compromised.
Potential Impact
Systems with this package installed are fully compromised. The attacker gains persistent code execution by modifying trusted package files outside the malicious package's own directory. The attacker can silently abuse the installer's authenticated WhatsApp session to follow arbitrary channels controlled by the attacker, potentially enabling further malicious activities or information leakage. Because the attacker controls a mutable GitHub-hosted channel list and response logic, the attack can evolve dynamically without republishing the package. All secrets and keys stored on the compromised system should be considered exposed and rotated immediately from a clean environment.
Mitigation Recommendations
No official patch or fix is currently available. The malicious package should be removed immediately. Due to the severity of the compromise and persistence mechanisms, the affected system should be considered fully compromised. All secrets and keys stored on the system must be rotated from a different, uncompromised device. Monitor for any use of the @whiskeysockets/baileys package and verify its integrity. Avoid installing packages that impersonate legitimate libraries and verify package authenticity before use.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6281
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-j2x4-j4hc-mvcv"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba8768715ace43581c1a
Added to database: 07/10/2026, 09:25:27 UTC
Last enriched: 07/10/2026, 10:05:24 UTC
Last updated: 07/25/2026, 17:01:52 UTC
Views: 8
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.