Malicious code in @trashcore/baileys (npm)
MAL-2026-18905 · GHSA-646c-v3qw-f7f9
Published · Modified
Dependency scanning
Check whether @trashcore/baileys is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
@trashcore/baileys is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own WhatsApp account to WhatsApp Channels chosen by the publisher. When the socket connects, code in lib/Socket/newsletter.js sends the WhatsApp w:mex FOLLOW query for the channel ID(s) 120363420249672073@newsletter, 120363424020283759@newsletter (stored as base64 strings), using the victim's authenticated session and without telling them. Same behaviour as the PhantomSub family (MAL-2026-17342).
__
Source: amazon-inspector (a919be08281949ba451753ba82050503c28d30c8c6abcd931c023234db01d261)
package.json declares the libsignal dependency as a bare git URL (git+https://github.com/whiskeysockets/libsignal-node) with no commit SHA, tag, or semver pin. On npm install, this dependency is resolved by cloning the default branch HEAD of that external GitHub repository and installing whatever code it currently contains, including any lifecycle scripts (preinstall/install/postinstall/prepare) present in the fetched tree. There is no integrity check, no version lock, and no cryptographic pinning — the executed code is determined by the state of a third-party repository at install time rather than by an immutable registry artifact. Whoever controls that external repository (or anyone who gains write access to its default branch) can introduce arbitrary code that will run on every machine that installs this package.
Source: ghsa-malware (7d631105bedd23f0da718b0af717dd140f0876f94caa047f46acfc1b4764ddbb)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes