raiden-baileys
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in raiden-baileys (npm)
Malicious package. raiden-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: 120363407277177688@newsletter, 120363407702752541@newsletter, 120363411769951302@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (b9372597423bda09fe5c3adc72b7ff804563626e2af777237b38d39563613de8)
package.json declares the libsignal dependency as github:RahmadTenpoles/libsignal-node with no commit SHA, tag, or integrity hash. On npm install, this resolves to whatever the default branch of that personal GitHub repository currently contains, including any lifecycle scripts, and executes them on the installer's machine. The source is a personal account unrelated to the official libsignal publisher, and the repository owner can push new code at any time to retroactively change what every subsequent install runs. The declared dependency key equals the standard name libsignal, so the override silently substitutes a third-party fork for what would otherwise resolve from the registry — a dependency-confusion-shaped override. The package also presents itself as a fork of the Baileys WhatsApp library (raiden-baileys), a lookalike naming pattern against the widely used @whiskeysockets/baileys family.
Not rated by the source.
0 (semver)None listed
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
Source: OpenSSF Malicious Packages · Apache-2.0