@ubedsockets/baileys@1.6.8
@ubedsockets/baileys,baileys A high-performance WhatsApp Web API wrapper based on Baileys, optimized for bot developers with integrated utility scrapers.
AI Security Review
scanned 13h ago · by lpm-firewall-aiThe socket factory automatically follows a hard-coded newsletter using the user's WhatsApp account, without consent. That is an unsolicited account action toward a publisher-selected target.
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
Creating a WhatsApp socket; the follow is scheduled 90 seconds later.
Impact
The user's account follows a target selected by the package publisher without a request from the user.
Mechanism
The newsletter module decodes a hard-coded newsletter ID and sends a FOLLOW mutation through the WhatsApp connection.
Attack narrative
When an application creates a WhatsApp socket, the package schedules a follow request for a hard-coded newsletter 90 seconds later. The request uses the user's authenticated WhatsApp connection and runs without an explicit user request, causing an account action toward a package-selected target.
AI rationale
The socket factory automatically follows a hard-coded newsletter using the user's WhatsApp account, without consent. That is an unsolicited account action toward a publisher-selected target.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.js
Network endpoints1
WhatsApp newsletter service via the existing WhatsApp connection
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package has no install lifecycle scripts; the behavior is triggered when a WhatsApp socket is created.
- Socket construction calls makeNewsletterSocket, which schedules a newsletter FOLLOW request 90 seconds later.
- The followed newsletter ID is hard-coded in Base64 and sent without user input or consent.
- Newsletter queries are sent through the WhatsApp newsletter protocol.
Evidence against
- The package presents itself as a WhatsApp Web API wrapper, so WhatsApp network access is expected.
- The flagged message utility files show no eval call in the inspected search results.
Behavioral surface
ChildProcessCryptoFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
GitDependency
Source & flagged code
8 flaggedlib/WABinary/constants.jsView file
603patternName = google_api_key
severity = high
line = 603
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603603patternName = google_api_key
severity = high
line = 603
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603WAProto/GenerateStatics.shView file
•path = WAProto/GenerateStatics.sh
kind = build_helper
sizeBytes = 301
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
WAProto/GenerateStatics.shView on unpkgFindings
6 High5 Medium3 Low
HighHigh Secretlib/WABinary/constants.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
HighSecret Patternlib/WABinary/constants.d.ts
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @ubedsockets/baileys@1.6.8.
See all versions of @ubedsockets/baileys for other recorded verdicts.
- Avoid installing @ubedsockets/baileys@1.6.8. 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.