@saazkira/baileys
This report shows the evidence for @saazkira/baileys@2.1.9. 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-17377 confirms this npm version as malicious.
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
The lifecycle hook is limited to a Node-version gate, and the network, file, and process primitives are exposed as media-library utilities rather than automatically chained during installation or import. Source inspection found no concrete malicious behavior.
Independent scan evidence
public snapshot- The exported upload helper sends a caller-provided buffer to public file-hosting services.
- Installation runs a Node-version check that can stop installs on Node versions below 20.
- Media thumbnail generation can invoke the locally installed ffmpeg executable.
- The preinstall script only reads the Node version and exits when it is below 20; it does not download, execute, or modify files.
- The upload and network functions are callable library utilities, not invoked by the install hook or package import path.
- No self-dependency, credential harvesting, hidden payload execution, persistence, or broad project mutation was found.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage 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 · L603Findings
Affected versions and remediation
This report applies to @saazkira/baileys@2.1.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing @saazkira/baileys@2.1.9. 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.