@lsqltmux-code/baileys@8.5.3
WhatsApp API Modification By Lsqltmux-Code
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe source confirms automatic, publisher-selected account actions when the socket is created. This concrete behavior supports blocking publication regardless of whether the install hook is benign.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer creates the package's socket through its exported factory.
Impact
The account is made to follow publisher-selected newsletters without the caller requesting those actions.
Mechanism
Nested socket constructors reach the newsletter socket, which schedules follow queries for three hardcoded newsletter identifiers.
Attack narrative
Creating the exported socket reaches newsletter socket construction through the package's socket layers. That constructor schedules three delayed newsletter queries using the follow action and fixed newsletter identifiers. The queries use the authenticated WhatsApp connection, so consumers can unknowingly cause their accounts to follow those newsletters.
AI rationale
The source confirms automatic, publisher-selected account actions when the socket is created. This concrete behavior supports blocking publication regardless of whether the install hook is benign.
Evidence
package.jsonlib/index.jslib/Socket/index.jslib/Socket/communities.jslib/Socket/business.jslib/Socket/messages-recv.jslib/Socket/messages-send.jslib/Socket/newsletter.js
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package entry point exports the socket factory, which reaches newsletter socket construction through its socket layers.
- Newsletter socket construction schedules three requests using the follow action and hardcoded newsletter identifiers, without a caller request or consent check.
- Those requests use the WhatsApp newsletter query protocol, making the authenticated account perform publisher-selected follows.
Evidence against
- The manifest's preinstall command only checks the Node.js version; the confirmed behavior is triggered later when the socket is constructed.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
GitDependency
Source & flagged code
9 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
6 High5 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/fix-import.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Fingerprint Signaturelib/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
Affected versions and remediation
This report applies to @lsqltmux-code/baileys@8.5.3.
See all versions of @lsqltmux-code/baileys for other recorded verdicts.
- Avoid installing @lsqltmux-code/baileys@8.5.3. 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.