zero2-baileys@3.6.0
WhatsApp API - NEW APDETE BAILEYS ZEROZ Edition
This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe active runtime path performs publisher-selected account actions without user invocation or a consent guard. This is concrete malicious behavior, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer creates the exported WhatsApp socket.
Impact
The connected account is subscribed to newsletters the consumer did not select.
Mechanism
The socket setup sends two follow queries for package-selected newsletter IDs after a 90-second delay, with no user action or consent check in this path.
Attack narrative
The exported socket factory reaches newsletter socket construction. That constructor schedules two follow operations for fixed newsletter IDs after 90 seconds; the requests use the WhatsApp query path and the package’s follow action identifier. This changes the connected account’s subscriptions without a caller-requested target.
AI rationale
The active runtime path performs publisher-selected account actions without user invocation or a consent guard. This is concrete malicious behavior, so publication should be blocked.
Evidence
package.jsonlib/index.jslib/Socket/index.jslib/Socket/registration.jslib/Socket/business.jslib/Socket/messages-recv.jslib/Socket/messages-send.jslib/Socket/newsletter.jslib/Types/Newsletter.js
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json sets lib/index.js as the package entry point.
- lib/index.js exports the socket factory.
- The socket factory constructs registration, business, receive, and send layers.
- The send layer creates the newsletter socket during construction.
- The newsletter query sends a follow action to WhatsApp with a supplied newsletter ID.
- Socket construction schedules follows of two fixed newsletter IDs after 90 seconds.
- The package maps the follow action to its newsletter protocol query ID.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
GitDependency
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.preinstall =
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.preinstall =
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkglib/VoIP/worker-bootstrap.jsView file
346const code = fs.readFileSync(url, "utf8");
L347: eval(code);
L348: }
Low
Eval
Package source references a known benign dynamic code generation pattern.
lib/VoIP/worker-bootstrap.jsView on unpkg · L346Findings
1 High9 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumUnsafe Vm Contextlib/VoIP/wasm-engine.js
MediumNetwork
MediumEnvironment Vars
MediumShips Wasm Modulelib/assets/wasm/whatsapp.wasm
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvallib/VoIP/worker-bootstrap.js
LowFilesystem
Low
Affected versions and remediation
This report applies to zero2-baileys@3.6.0.
See all versions of zero2-baileys for other recorded verdicts.
- Avoid installing zero2-baileys@3.6.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.