libsignal-node-travatigernpm
libsignal-node-travatiger is a confirmed malicious npm package (MAL-2026-6281) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in libsignal-node-travatiger (npm)
What this malware does
On require() of this package, index.js schedules install.js which locates @whiskeysockets/baileys in the installer's node_modules tree (searching process.cwd(), parent directories, and require.resolve) and overwrites lib/Socket/newsletter.js with an attacker-controlled replacement. A.cache marker is dropped to make the patch idempotent and persistent across reinstalls. The replacement newsletter.js, once the installer uses Baileys with their authenticated WhatsApp session, runs a setTimeout (~120s after socket creation) that fetches https://raw.githubusercontent.com/travatiger/MegaTeam/main/channel.json — a mutable, attacker-controlled URL — and invokes WhatsApp's newsletter FOLLOW mutation (newsletterWMexQuery with Types_1.QueryIds.FOLLOW) for each returned channel ID, silently using the installer's authenticated WhatsApp identity to follow channels chosen by the attacker. Because the channel list lives in a mutable GitHub repo, the attacker can change targets — or, more dangerously, the response-handling logic — at any time without republishing the npm package. The package name impersonates the legitimate libsignal-node Signal Protocol library and the description claims 'Modified libsignal for Node.js' to lend legitimacy to the lure. Three independent harms: (1) tampering with a sibling trusted package's on-disk source, (2) install-time persistence outside this package's own directory, (3) silent relay/abuse of the installer's authenticated WhatsApp session for attacker benefit.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for libsignal-node-travatiger (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging libsignal-node-travatiger across your stack and pipelines.
If you installed it — respond
libsignal-node-travatiger is a typosquat — you almost certainly intended a legitimately-named package. Remove libsignal-node-travatiger, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If libsignal-node-travatiger was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks libsignal-node-travatiger before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks libsignal-node-travatiger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.