@denzz221/baileys
A WebSockets library for interacting with WhatsApp Web.
This report shows the evidence for @denzz221/baileys@2.0.0. 11 of 11 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 26m ago · by lpm-firewall-aiThe package automatically follows a hard-coded WhatsApp newsletter through the user’s session when its client socket is constructed. This is an unrequested account action toward a target selected by the publisher.
Decision evidence
public snapshot- Creating the newsletter socket schedules a delayed follow request for a hard-coded newsletter ID encoded in base64.
- The request decodes the ID and invokes the WhatsApp newsletter FOLLOW operation without an explicit user request.
- The newsletter socket is constructed by the username socket, which is used by the message socket; the package’s socket factory assembles the client layers.
- The preinstall hook runs engine-requirements.js, which only checks the Node.js major version and exits for versions below 20.
- The follow request is sent through the WhatsApp w:mex protocol, consistent with the package’s WhatsApp client functionality.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Findings
Affected versions and remediation
This report applies to @denzz221/baileys@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @denzz221/baileys@2.0.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.