registry / Data exfiltration / xzvbails
xzvbails
hello I am RxVz, I am a student trying to develop a WhatsApp library via baileys and this is my baileys xzbails
This report shows the evidence for xzvbails@0.0.1, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package contains an exported runtime path that exfiltrates supplied phone numbers to an unrelated host with a deliberately abusive header. Although not automatic, this is concrete malicious data collection behavior.
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 calls the socket object's checkBan(number) method.
Impact
Phone numbers supplied by consumers are disclosed to the external host.
Mechanism
Third-party HTTP request containing a phone number.
Attack narrative
The socket factory exposes checkBan. When called, it normalizes the provided phone number and places it in a GET request to xzc-corporation.biz.id, a host unrelated to the WhatsApp service APIs used elsewhere. The request also carries an offensive custom header. This discloses user-supplied phone numbers to a third party without a package-aligned service endpoint.
AI rationale
The package contains an exported runtime path that exfiltrates supplied phone numbers to an unrelated host with a deliberately abusive header. Although not automatic, this is concrete malicious data collection behavior.
Evidence
lib/Socket/socket.js
Network endpoints1
xzc-corporation.biz.id
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The exported checkBan method sends the supplied phone number to an unrelated third-party host.
- The request includes an offensive custom header, indicating deliberate nonstandard behavior.
- The method is returned by the socket factory and is callable by package consumers.
Evidence against
- The transfer is triggered only when a consumer calls checkBan; it is not install-time or import-time.
- The preinstall hook only checks the Node.js major version and exits for versions below 20.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
Source & flagged code
9 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 · L600lib/Utils/validate-connection.js
Findings
6 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
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
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
Affected versions and remediation
This report applies to xzvbails@0.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing xzvbails@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.