@lekzox/baileys
WhatsApp API Modification By Lekzo
This report shows the evidence for @lekzox/baileys@0.0.1. 1 of 2 known versions is blocked or flagged. See all versions.
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 8d ago · by lpm-firewall-aiSource inspection confirms a reachable, automatic account follow action for a fixed target during ordinary socket construction. This unrequested account mutation supports blocking the package.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Calling the exported makeWASocket constructor.
Impact
The consumer's WhatsApp account may follow the selected newsletter without the consumer requesting that action.
Mechanism
The reachable newsletter socket layer schedules a WhatsApp follow request for a fixed newsletter ID after 90 seconds, without an opt-in or caller-selected target.
Attack narrative
Calling makeWASocket reaches makeNewsletterSocket through the socket constructor chain. That constructor unconditionally schedules a WhatsApp follow request for a fixed newsletter ID after 90 seconds. The request uses the package's WhatsApp query path and has no caller opt-in or target selection guard, so it can change the consumer's account by following a publisher-selected newsletter.
AI rationale
Source inspection confirms a reachable, automatic account follow action for a fixed target during ordinary socket construction. This unrequested account mutation supports blocking the package.
Evidence
lib/index.jslib/Socket/index.jslib/Socket/communities.jslib/Socket/business.jslib/Socket/messages-recv.jslib/Socket/messages-send.jslib/Socket/username.jslib/Signal/Group/Protocols.jslib/Socket/mex.jslib/Types/Mex.js
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The main export exposes a socket constructor that builds the community socket layer.
- The constructor chain reaches the newsletter socket through the community, business, receive, send, and username layers.
- Newsletter socket construction unconditionally schedules a follow request for a fixed newsletter ID after 90 seconds.
- The request uses the WhatsApp query path and the FOLLOW protocol action.
Evidence against
- The preinstall hook only checks the Node.js major version and exits on unsupported versions.
- The scheduled follow request suppresses errors, but has no caller opt-in or target selection guard.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
GitDependency
Source & flagged code
8 flagged · loading sourcepackage.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
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
Affected versions and remediation
This report applies to @lekzox/baileys@0.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lekzox/baileys@0.0.1. 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.