@ubedsockets/baileys@1.7.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 package automatically uses the user's WhatsApp credentials to follow a hard-coded newsletter when its connection opens, an account action the user did not request. Its socket setup also imposes an unrelated IP allowlist and exits the host process when the check fails.
Decision evidence
public snapshot- The package entry point is lib/index.js and package.json declares no lifecycle scripts.
- The default makeWASocket creates the normal business socket stack.
- The message socket constructs the newsletter socket as part of socket creation.
- When the WhatsApp connection opens, the code checks a hard-coded newsletter and follows it if the account is not already subscribed.
- Creating the base socket also sends a request to api.ipify.org and exits the host process if the IP check fails or the IP is not allowlisted.
- The package is described as a WhatsApp Web API wrapper, so connecting to WhatsApp is expected.
- The manifest has no install lifecycle scripts.
Source & flagged code
11 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 · L603Findings
Affected versions and remediation
This report applies to @ubedsockets/baileys@1.7.9.
See all versions of @ubedsockets/baileys for other recorded verdicts.
- Avoid installing @ubedsockets/baileys@1.7.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.