@monze1239/baileys@1.0.1
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 2h ago · by lpm-firewall-aiSocket construction schedules an authenticated WhatsApp follow action toward a hard-coded newsletter, without an explicit user request. This is a concrete account action benefiting a publisher-selected target, so the package is malicious.
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
Calling the package's makeWASocket factory; the follow is scheduled for 10 seconds later.
Impact
The user's WhatsApp account follows a channel without an explicit request, artificially increasing the selected channel's followers.
Mechanism
The socket layers construct makeNewsletterSocket, which schedules a FOLLOW query for a hard-coded newsletter ID decoded from base64 and sends it over the WhatsApp w:mex protocol.
Attack narrative
When an application constructs this package's WhatsApp socket, the layered factory reaches makeNewsletterSocket. That constructor schedules a FOLLOW request roughly 10 seconds later for a fixed newsletter ID encoded in the source. The request uses the user's authenticated WhatsApp connection, so the account follows the selected channel without the user's request.
AI rationale
Socket construction schedules an authenticated WhatsApp follow action toward a hard-coded newsletter, without an explicit user request. This is a concrete account action benefiting a publisher-selected target, so the package is malicious.
Evidence
lib/Socket/index.jslib/Socket/communities.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 exported socket factory constructs the socket layers that reach makeNewsletterSocket.
- makeNewsletterSocket schedules a WhatsApp newsletter FOLLOW request after 10 seconds, using a hard-coded newsletter ID encoded in base64.
- The follow request is sent through the WhatsApp socket using a w:mex query.
- The preinstall hook only checks that Node.js is version 20 or newer.
Evidence against
- The package is presented as a WhatsApp Web socket library, where sending requests through an authenticated WhatsApp socket is expected.
- Other newsletter follow methods accept a caller-supplied JID, but the scheduled follow runs automatically during socket construction.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
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
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 @monze1239/baileys@1.0.1.
See all versions of @monze1239/baileys for other recorded verdicts.
- Avoid installing @monze1239/baileys@1.0.1. 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.