@rennnpm/baileys
A WebSockets library for interacting with WhatsApp Web — Renn Baileys fork
This report shows the evidence for @rennnpm/baileys@1.0.0, the only known version.
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-17374 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 a transparent Node.js version guard, and the flagged high-signal files contain normal media-processing and protocol-table code. Static inspection found no concrete malicious behavior.
Independent scan evidence
public snapshot- The install hook runs a local Node.js version check.
- Video thumbnail support constructs an ffmpeg shell command.
- Business image handling writes supplied media to a temporary file before a caller-provided upload operation.
- The flagged constants file is a WhatsApp protocol token table, not an embedded credential.
- The install hook only reads the running Node version and exits for unsupported versions.
- No credential harvesting, environment collection, exfiltration endpoint, persistence, self-dependency, or agent-control mutation was found.
- The ffmpeg path is generated in the system temporary directory before thumbnail creation.
- Network operations implement requested WhatsApp media and version functions.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Findings
Affected versions and remediation
This report applies to @rennnpm/baileys@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @rennnpm/baileys@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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.