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-18951 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-18951 confirms this npm version as malicious.
Advisory
MAL-2026-18951
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in bintzge-baileys (npm)
Details
bintzge-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) 120363364987398307@newsletter, 120363390026302997@newsletter, 120363401467939056@newsletter, 120363407277177688@newsletter (stored as base64 strings), using the victim's authenticated session and without telling them. Same behaviour as the PhantomSub family (MAL-2026-17342).
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package adds fixed publisher newsletter attribution to outgoing event messages, a behavior users of the WhatsApp library may not expect. The feature runs only when an event message is sent, so the evidence supports a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The application using the socket sends an EVENT message.
Impact
Recipients may see publisher-selected channel attribution attached to messages sent through the user's WhatsApp account.
Mechanism
The added handler attaches BintzTech newsletter metadata to the outgoing event and relays it to the requested recipient.
AI called this Suspicious at 87.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
When the caller sends an EVENT message, the socket routes it through the added handleEvent method.
That method embeds the publisher-branded newsletter name and fixed newsletter JID 120363364987398307@newsletter in the outgoing event message, then relays it to the caller-supplied recipient.
Evidence against
The preinstall hook only runs engine-requirements.js, which checks the Node version and exits on versions below 20.
The newsletter attribution is added during an explicitly triggered event-message send; the reviewed code does not show automatic channel joining or a background send.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing bintzge-baileys@2.0.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.