ndraawzz-baileys@1.5.0
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe normal socket creation path schedules a follow action toward a hard-coded WhatsApp newsletter without user consent. This is an unsolicited account action and warrants blocking publication.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Calling the normal socket creation path, which constructs the messages, username, and newsletter socket layers.
Impact
The user’s WhatsApp account may follow a newsletter selected by the package publisher.
Mechanism
The newsletter socket decodes a hard-coded newsletter ID and sends a FOLLOW query after a 10-second delay. The action is not gated on a user request or consent setting.
Attack narrative
When the package’s normal socket creation path builds a messages socket, it also builds a username socket and newsletter socket. The newsletter socket schedules a WhatsApp FOLLOW request for a hard-coded newsletter ID after 10 seconds. This uses the connected account to follow a publisher-selected target without an explicit user request.
AI rationale
The normal socket creation path schedules a follow action toward a hard-coded WhatsApp newsletter without user consent. This is an unsolicited account action and warrants blocking publication.
Evidence
lib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.js
Network endpoints1
wss://web.whatsapp.com/ws/chat
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating a messages socket constructs the username socket, which constructs the newsletter socket.
- The newsletter socket schedules a FOLLOW request for a hard-coded newsletter ID after a 10-second delay, without checking for user consent.
- The package’s preinstall script only checks whether Node.js is version 20 or newer.
Evidence against
- The package is described as a WebSockets library for interacting with WhatsApp Web, and its default connection URL is WhatsApp’s web socket endpoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
Source & flagged code
8 flaggedpackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/WABinary/constants.jsView file
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Findings
5 High5 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis Limitedlib/Utils/business.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
Low
Affected versions and remediation
This report applies to ndraawzz-baileys@1.5.0.
See all versions of ndraawzz-baileys for other recorded verdicts.
- Avoid installing ndraawzz-baileys@1.5.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.