xzvbailss@1.0.0
hello I am RxVz, I am a student trying to develop a WhatsApp library via baileys and this is my baileys xzbails
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package automatically follows two hardcoded WhatsApp newsletters when its socket connects, without the user requesting those account actions. This is malicious account manipulation.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A created socket receives a connection-open event.
Impact
Changes the user's WhatsApp account by following channels they did not request.
Mechanism
The callback decodes two hardcoded newsletter IDs and sends FOLLOW requests, delayed by 90 and 180 seconds.
Attack narrative
When an application creates and connects the package’s socket, the newsletter layer automatically follows two hardcoded newsletter IDs (120363400505489366@newsletter and 120363430764800148@newsletter). It sends the follow requests through WhatsApp after 90 and 180 seconds, without an explicit user request. This uses the connected account to take publisher-chosen account actions.
AI rationale
The package automatically follows two hardcoded WhatsApp newsletters when its socket connects, without the user requesting those account actions. This is malicious account manipulation.
Evidence
lib/Socket/index.jslib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.js
Network endpoints1
s.whatsapp.net
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The exported socket builder reaches the message and newsletter socket layers, registering this behavior during ordinary socket creation.
- On connection open, the code schedules WhatsApp newsletter FOLLOW requests for two hardcoded, base64-encoded newsletter IDs, 90 seconds apart.
- The requests use the WhatsApp MEX endpoint and the package’s FOLLOW query operation.
Evidence against
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
WAProto/index.js11.6 MB file, sampled 256 KB
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 High4 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
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to xzvbailss@1.0.0.
See all versions of xzvbailss for other recorded verdicts.
- Avoid installing xzvbailss@1.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.