@ubedsockets/baileys@1.6.1
@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 package automatically uses the user's WhatsApp account to follow a publisher-selected newsletter when a socket is created, and also sends default reactions to newsletter messages. The unrequested follow is concrete account-abuse behavior, despite the package's legitimate WhatsApp client purpose.
Decision evidence
public snapshot- Creating the package’s socket constructs the newsletter socket as part of the normal send-socket setup.
- Newsletter reactions are enabled by default and sent for fetched newsletter messages.
- A 90-second timer decodes a hard-coded newsletter ID and issues a FOLLOW query automatically.
- The package entry point exports makeWASocket, which creates the socket used by that setup.
- The package is described as a WhatsApp Web API wrapper, so WhatsApp network and newsletter protocol code are expected.
- The manifest defines no lifecycle scripts.
Source & flagged code
7 flaggedPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603Package ships non-JavaScript build or shell helper files.
WAProto/GenerateStatics.shView on unpkgFindings
Affected versions and remediation
This report applies to @ubedsockets/baileys@1.6.1.
See all versions of @ubedsockets/baileys for other recorded verdicts.
- Avoid installing @ubedsockets/baileys@1.6.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.