This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-18905 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-18905 confirms this npm version as malicious.
Advisory
MAL-2026-18905
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @trashcore/baileys (npm)
Details
@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.
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The manifest has no active prepare or prepack behavior, and the reviewed custom message paths require a caller-provided sendMessage request. The flagged newsletter IDs occur in message metadata rather than an automatic account action, and no unrelated collection or transfer was identified.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
No malicious automatic trigger identified. Custom message handling runs when the caller invokes sendMessage.
Impact
No unauthorized data transfer or account action identified.
Mechanism
The fixed newsletter ID is included as forwarded-message metadata; it is not used as the recipient or to perform an account action.
Independent scan evidence
public snapshot
AI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The manifest’s prepare and prepack scripts are empty; it declares no install hook.
The package entry point exports the socket and library modules.
Custom message handlers are dispatched from the socket’s sendMessage method, which takes a caller-supplied destination and content.
The flagged newsletter ID appears in outgoing event-message metadata, not as an automatic subscription or message destination.
Evidence against
The package is described as a modified WhatsApp Web API library, consistent with its socket, message, and media-handling code.
Media helpers use network and filesystem APIs for WhatsApp media features; no unrelated collector or credential transfer was identified.
The source-similarity hints concern utility files, and review found no concrete attack behavior in them.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @trashcore/baileys@4.2.7. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.