@dcloude/baileys
WhatsApp Baileys Library Modification to make it easier for developers to develop for anything
This report shows the evidence for @dcloude/baileys@0.1.2. 2 of 6 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe socket follows many publisher-selected WhatsApp channels automatically when it connects, using the user's account. This is an unrequested account action and meets the malicious verdict criteria even though the behavior is documented and opt-out.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The application creates a socket and it connects successfully, unless the caller disables or overrides autoFollowChannels.
Impact
The user's account subscribes to numerous channels they did not choose.
Mechanism
A connection event handler sends a WhatsApp FOLLOW query for every JID in the default channel list.
Attack narrative
When a socket connects, the package automatically follows a large baked-in list of WhatsApp newsletter channels. This uses the user's authenticated account to perform subscriptions toward targets chosen by the publisher, without a request from the user. The behavior is documented and can be disabled, but it remains on by default.
AI rationale
The socket follows many publisher-selected WhatsApp channels automatically when it connects, using the user's account. This is an unrequested account action and meets the malicious verdict criteria even though the behavior is documented and opt-out.
Evidence
lib/Defaults/index.jslib/Socket/newsletter.jslib/Socket/index.js
Network endpoints1
WhatsApp (s.whatsapp.net)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The default connection configuration assigns a baked-in list of WhatsApp newsletter JIDs to autoFollowChannels.
- On the first successful connection, the socket follows every configured JID automatically.
- The follow request uses WhatsApp's FOLLOW query and submits each newsletter ID through a WhatsApp query.
- Socket construction applies the default configuration when the caller omits options.
Evidence against
- The auto-follow behavior and its disable option are documented in source comments.
- The preinstall script only checks that Node.js is version 20 or newer.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/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 · L600Findings
5 High6 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumDynamic Requirelib/antiban.cjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Crypto
Affected versions and remediation
This report applies to @dcloude/baileys@0.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dcloude/baileys@0.1.2. 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.