@zyrennofficiall/baileys@5.3.0
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe package performs an unrequested account action by following a publisher-selected WhatsApp channel whenever a connection opens. This behavior is enabled by default, so the package is malicious under the account-action rule.
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
By default, after a socket connection opens.
Impact
The user's WhatsApp account follows a channel without an explicit request.
Mechanism
makeWASocket registers a connection handler that calls newsletterFollow with a hard-coded newsletter ID; the behavior can be disabled with autoFollow: false.
Attack narrative
When a client creates a socket and connects, the package follows the hard-coded newsletter 120363430929084263@newsletter by default. The package exposes an opt-out, but a default the user must disable is not an explicit request. The follow method sends the newsletter ID through WhatsApp's newsletter follow operation.
AI rationale
The package performs an unrequested account action by following a publisher-selected WhatsApp channel whenever a connection opens. This behavior is enabled by default, so the package is malicious under the account-action rule.
Evidence
lib/Socket/index.jslib/Defaults/index.jslib/Socket/newsletter.js
Network endpoints2
web.whatsapp.comwhatsapp.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- makeWASocket follows the hard-coded WhatsApp newsletter when the connection opens unless autoFollow is explicitly false.
- autoFollow defaults to true.
- newsletterFollow sends a WhatsApp newsletter follow request using the supplied newsletter ID.
Evidence against
- The preinstall script only runs a Node version check and exits for versions below 20.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
WAProto/index.js11.6 MB file, sampled 256 KB
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
6 High4 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis Limitedlib/Utils/business.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
Affected versions and remediation
This report applies to @zyrennofficiall/baileys@5.3.0.
See all versions of @zyrennofficiall/baileys for other recorded verdicts.
- Avoid installing @zyrennofficiall/baileys@5.3.0. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.