Advisory

MAL-2026-6281

Also known as: GHSA-j2x4-j4hc-mvcv

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in libsignal-node-travatiger (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (311b53330c1d8c3546d0b4fa3d460ca694fc20d60608ac5a276f40f7a73279fa)
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.

Source: ghsa-malware (853bda071feb857da7ff2ecaa7809099b31dd181eed007bb9593b0e274e8a8be)
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.

Severity

Not rated by the source.

Dates

Published
2026-06-23 11:57 UTC
Modified
2026-07-09 17:31 UTC

Affected packages and fixes

libsignal-node-travatiger

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences