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.
## 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 suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
Video thumbnail generation interpolates a local media path into a command passed to child_process.exec, creating a shell injection vulnerability when the path is attacker-controlled. The path is reached during thumbnail processing, so this is a vulnerability finding rather than evidence of an automatic attack.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A caller provides a local video path containing shell metacharacters and requests media processing that needs a thumbnail.
Impact
An attacker able to control that path may execute commands with the Node process's permissions.
Mechanism
The path is passed into a command string and executed with child_process.exec.
Evidence
lib/Utils/messages-media.jslib/Utils/messages.js
Independent scan evidence
public snapshot
AI called this Suspicious at 84.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for AI warning decision
When a video needs a thumbnail, message preparation calls the thumbnail generator.
For local file input, the media path is used directly as the processing path.
Video thumbnail generation interpolates that path into a command string passed to child_process.exec, allowing shell metacharacters in the path to execute commands.
The package entry point exports the socket API; the identified execution path is media processing, not import-time behavior.
Evidence against
The ffmpeg command is used for the package's video thumbnail feature.
The vulnerable path requires a caller to provide a local video path and trigger thumbnail generation; no install-time or import-time attack was identified.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @trashcore/baileys@4.2.6. 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.