@ubedsockets/baileys@1.6.9
@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 normal socket creation path starts a timer that follows a hard-coded WhatsApp newsletter after 90 seconds. This is an unrequested account action toward a target chosen by the package publisher, so the version is malicious.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Creating a WhatsApp socket; the action runs 90 seconds later.
Impact
Uses the user’s WhatsApp account to follow a publisher-chosen newsletter.
Mechanism
The newsletter socket decodes a fixed newsletter ID and sends a WhatsApp FOLLOW query without an explicit follow request.
Attack narrative
When a WhatsApp socket is created, the package schedules a delayed task that decodes a fixed newsletter ID and sends a FOLLOW query. This uses the user’s account to follow a publisher-chosen target without an explicit request.
AI rationale
The normal socket creation path starts a timer that follows a hard-coded WhatsApp newsletter after 90 seconds. This is an unrequested account action toward a target chosen by the package publisher, so the version is malicious.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.jslib/Socket/index.js
Network endpoints1
s.whatsapp.net
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the normal WhatsApp socket constructs the messages socket, which constructs the newsletter socket.
- The newsletter socket starts a timer that decodes a hard-coded newsletter ID and sends a FOLLOW query after 90 seconds.
- The follow occurs without a request to follow that newsletter; it uses the socket’s WhatsApp connection.
Evidence against
- The manifest has no install lifecycle scripts; the behavior is triggered at runtime when a socket is created.
- The package is a WhatsApp API wrapper, so its WhatsApp protocol traffic is expected; the fixed, automatic follow is not part of an explicitly requested action.
Behavioral surface
ChildProcessCryptoFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
GitDependency
Source & flagged code
6 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
4 High5 Medium3 Low
HighHigh Secretlib/WABinary/constants.js
HighKnown Malware Source Similaritylib/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
LowUrl Strings
Affected versions and remediation
This report applies to @ubedsockets/baileys@1.6.9.
See all versions of @ubedsockets/baileys for other recorded verdicts.
- Avoid installing @ubedsockets/baileys@1.6.9. 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.