@sakataa/baileys@2.0.0
A WebSockets library for interacting with Customize WhatsApp.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe socket constructor triggers authenticated WhatsApp follow actions toward hard-coded targets without user consent. This is malicious account manipulation, even though the install hook only checks the Node.js version.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Calling the package's socket constructor.
Impact
The user's account is made to follow newsletters selected by the package publisher.
Mechanism
The newsletter socket schedules four WhatsApp newsletter follow mutations to hard-coded IDs without a caller request or consent check.
Attack narrative
When a caller constructs the socket, the package builds the newsletter layer, which schedules four follow mutations to hard-coded newsletter IDs within 10 to 25 seconds. The requests use the user's authenticated WhatsApp socket, changing account state toward targets chosen by the publisher without a request to follow them.
AI rationale
The socket constructor triggers authenticated WhatsApp follow actions toward hard-coded targets without user consent. This is malicious account manipulation, even though the install hook only checks the Node.js version.
Evidence
lib/Socket/index.jslib/Socket/business.jslib/Socket/messages-recv.jslib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.jslib/Socket/mex.js
Network endpoints1
web.whatsapp.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The public socket builder constructs the business, receive, and message socket layers, which create the username and newsletter sockets.
- Newsletter socket construction schedules four follow requests to hard-coded newsletter IDs after delays of 10 to 25 seconds, without requiring a follow request from the caller.
- The follow mutations are sent through the WhatsApp socket query path.
Evidence against
- The preinstall script only checks the Node.js major version and exits for versions below 20.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
Source & flagged code
8 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 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
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
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @sakataa/baileys@2.0.0.
See all versions of @sakataa/baileys for other recorded verdicts.
- Avoid installing @sakataa/baileys@2.0.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.