@zaidevx/baileys@1.0.4
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package automatically uses the connected WhatsApp account to follow newsletters chosen by a remote list controlled by the publisher. This is an unsolicited account action, so the package is malicious.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Normal construction of the message socket, followed by the user's WhatsApp connection opening.
Impact
Uses the connected account to follow targets chosen by the package publisher without the user's request.
Mechanism
The newsletter socket fetches a Base64-obscured channel list from raw.githubusercontent.com, then sends WhatsApp MEX follow requests for each listed newsletter ID.
Attack narrative
When normal message-socket construction reaches the newsletter socket, it fetches a publisher-controlled list of newsletter IDs. Once the user's WhatsApp connection opens, it schedules follow requests for every listed ID through the authenticated WhatsApp connection, without requiring the user to request or approve those follows.
AI rationale
The package automatically uses the connected WhatsApp account to follow newsletters chosen by a remote list controlled by the publisher. This is an unsolicited account action, so the package is malicious.
Evidence
lib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.js
Network endpoints2
raw.githubusercontent.com/mmhdzaidie-dev/idch/refs/heads/main/channel.jsons.whatsapp.net (w:mex)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package's main export points to its JavaScript client entry point.
- Constructing the message socket constructs the username socket, which constructs the newsletter socket.
- The newsletter socket decodes a hard-coded URL for a remote channel list.
- The socket fetches that list automatically and accepts newsletter IDs from it.
- After the WhatsApp connection opens, it schedules follow requests for each listed ID without an explicit user request.
Evidence against
- The package is a WhatsApp Web client, and it provides an explicit newsletter-follow API.
- The observed follow requests go to WhatsApp through its normal MEX query mechanism; the separate remote request retrieves the list of targets.
Behavioral surface
ChildProcessCryptoDynamicRequireFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggedlib/WABinary/constants.jsView file
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600lib/antiban.cjsView file
1const __importMetaUrl = require('url').pathToFileURL(__filename).href
L2: ;('use strict')
Medium
Dynamic Require
Package source references dynamic require/import behavior.
lib/antiban.cjsView on unpkg · L1Findings
5 High5 Medium6 Low
HighHigh Secretlib/WABinary/constants.js
HighBase64 Obscured Urllib/Socket/newsletter.js
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumDynamic Requirelib/antiban.cjs
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
Affected versions and remediation
This report applies to @zaidevx/baileys@1.0.4.
See all versions of @zaidevx/baileys for other recorded verdicts.
- Avoid installing @zaidevx/baileys@1.0.4. 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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.