Advisory

MAL-2026-18787

Also known as: GHSA-fjhf-q8f8-r96j

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

Summary

Malicious code in @chatbridgeworld/baileys (npm)

Details

Malicious package. @chatbridgeworld/baileys is a trojanized fork of the Baileys WhatsApp library (@whiskeysockets/baileys). on connection it issues an authenticated w:mex newsletter FOLLOW mutation (query_id 7871414976211147) that silently subscribes every victim to attacker-controlled WhatsApp channels — hardcoded newsletter JIDs: 120363297591152843@newsletter, 120363351424590490@newsletter, 120363410165027550@newsletter, 120363412935005237@newsletter, 120363413699154858@newsletter, 120363413933221020@newsletter, 120363426302817140@newsletter, 120363428923746817@newsletter, 120363430013410680@newsletter, 120363433092350168@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious. Detected by wormsign static analysis of the injected channel-subscription code.

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

Source: amazon-inspector (fec4c590590e68769337688429a7da8c011f695e51e6f39cbd00910317d2fc45)
package.json for @chatbridgeworld/[email protected] declares the libsignal dependency as github:chatbridgegit/libsignal-node — a bare GitHub tree reference with no commit SHA and no version pin. On npm install, npm fetches whatever the default branch of that repository currently points at and executes any lifecycle scripts contained in those bytes, with no integrity check and no reproducibility guarantee across installs. Whoever controls the chatbridgegit/libsignal-node repository can push arbitrary code into every subsequent install of this package. The dependency name (libsignal) also matches the host package's own ecosystem naming (Baileys forks typically depend on the npm-published libsignal-node), consistent with a dependency-source redirection shape.

Source: ghsa-malware (b7a5a2853e26ae8d922803db487eb05b9a6f8ae50d426750c0a5cd1d5ca208ab)
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-11-09 16:26 UTC
Modified
2026-11-13 03:45 UTC

Affected packages and fixes

@chatbridgeworld/baileys

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