@ubedsockets/baileys@1.2.0
@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 performs a publisher-selected WhatsApp follow automatically after socket creation. The account-action rules classify using a user's credentials for an unrequested action toward a publisher-chosen target as malicious.
Decision evidence
public snapshot- The package has no lifecycle scripts; its main entry is lib/index.js.
- Default socket construction reaches makeNewsletterSocket through makeMessagesSocket.
- makeNewsletterSocket schedules a FOLLOW request 90 seconds after socket creation for a fixed newsletter ID encoded in the source.
- Newsletter updates also trigger automatic 👍 reactions to messages with server IDs.
- The package describes itself as a WhatsApp Web API wrapper, so WhatsApp protocol traffic is expected.
- The follow and reactions use WhatsApp's newsletter protocol; no unrelated collector or credential theft was identified.
Source & flagged code
6 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.2.0.
See all versions of @ubedsockets/baileys for other recorded verdicts.
- Avoid installing @ubedsockets/baileys@1.2.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.