@raffnotdev/baileys
A WebSockets library for interacting with WhatsApp Web.
This report shows the evidence for @raffnotdev/baileys@1.0.0, the only known version.
AI Security Review
scanned 2h ago · by lpm-firewall-aiClient construction schedules unsolicited follows of four publisher-selected WhatsApp channels using the user's account. This is concrete account abuse and warrants blocking publication.
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
The application creates a Baileys socket; delayed follow requests are scheduled during socket construction.
Impact
Uses the user's WhatsApp account to perform account actions toward targets the publisher chose, without the user's request.
Mechanism
The newsletter socket decodes four hard-coded channel IDs and sends FOLLOW queries after delays of 10 to 25 seconds.
Attack narrative
When an application creates the exported socket, the construction chain instantiates the newsletter socket. That constructor schedules four delayed FOLLOW requests for hard-coded, base64-encoded newsletter IDs. The requests use the user's WhatsApp connection and do not require the user to ask to follow those channels.
AI rationale
Client construction schedules unsolicited follows of four publisher-selected WhatsApp channels using the user's account. This is concrete account abuse and warrants blocking publication.
Evidence
lib/Socket/newsletter.jslib/Socket/username.jslib/Socket/messages-send.jslib/Socket/messages-recv.jslib/Socket/business.jslib/Socket/communities.jslib/Socket/index.js
Network endpoints1
wss://web.whatsapp.com/ws/chat
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the newsletter socket schedules four delayed requests that decode hard-coded newsletter IDs and issue FOLLOW operations.
- The exported socket construction chain reaches that newsletter socket, so creating a client triggers these follows without a request to follow those channels.
Evidence against
- The preinstall hook only checks the Node.js version and exits when it is below 20; no install-time network or file activity was found.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
WAProto/index.js
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 @raffnotdev/baileys@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @raffnotdev/baileys@1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.