@jojoxyz/condemnedforce-baileys
This report shows the evidence for @jojoxyz/condemnedforce-baileys@2.3.0. 1 of 3 known versions is 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 12d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17360 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 install hook only enforces a Node version requirement, and the flagged network operation retrieves caller-selected media. No concrete malicious behavior was established.
Independent scan evidence
public snapshot- package.json configures preinstall to run a Node version check.
- engine-requirements.js exits only when the Node major version is below 20.
- The media utility performs an HTTP fetch for caller-provided media URLs.
- The package entrypoint clears the terminal and prints a banner during import.
- Inspected lifecycle code does not install dependencies, mutate project files, or contact a network endpoint.
- Inspected entrypoint and media-fetch behavior show no credential harvesting or exfiltration.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json configures preinstall to run a Node version check.
package.jsonView on unpkg · L27Package contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @jojoxyz/condemnedforce-baileys@2.3.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @jojoxyz/condemnedforce-baileys@2.3.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.