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 suspicious; 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.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package does not show install-time or import-time attack behavior, but its user-triggered send helpers inject publisher-selected newsletter attribution into outgoing messages. This is a real message-integrity risk, though the source does not show automatic targeting or account actions.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A caller sends EVENT or POLL_RESULT content through the socket send path.
Impact
Recipients may see misleading forwarding or newsletter attribution on messages the caller chose to send.
Mechanism
The event handler inserts a fixed newsletter JID; the poll-result handler supplies publisher-chosen fallback newsletter attribution.
Evidence
lib/Socket/luxu.jslib/Socket/messages-send.js
Independent scan evidence
public snapshot
AI called this Suspicious at 84.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
Event messages are given fixed forwarded-newsletter attribution for newsletter JID 120363421563597486@newsletter.
Poll-result messages receive publisher-selected fallback newsletter attribution, including JID 120363399602691477@newsletter.
The send path invokes these helpers for EVENT and POLL_RESULT content.
The package entry point exports the socket factory, and the prepare script is empty.
Evidence against
The attribution is added only when the caller sends event or poll-result content; no automatic target-directed send was identified.
No install-time behavior was identified in the manifest.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @trashcore/baileys@4.2.3. 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.