baileys-xbats
This report shows the evidence for baileys-xbats@1.0.0. 4 of 6 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. 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.
OpenSSF/OSV Malicious Advisory
imported 23d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17388 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The callable uploader transfers arbitrary supplied buffers to unrelated public hosts and has no destination restriction or consent gate. It is not automatically activated, so the evidence supports a warning rather than a publication block.
Independent scan evidence
public snapshot- The public utility module exports an uploadFile function.
- uploadFile places its buffer argument in multipart form data for public file-hosting services.
- The function posts that form to each configured service until one succeeds.
- package.json has no lifecycle scripts.
- No package-internal caller of uploadFile was found; it requires an explicit API call.
- The dynamic import is a fixed audio-decode module name, not caller-controlled code.
Source & flagged code
8 flagged · loading sourcePackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603Source file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to baileys-xbats@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing baileys-xbats@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.