ynastore-baileys
WhatsApp API Modification
This report shows the evidence for ynastore-baileys@1.0.21. 1 of 2 known versions is blocked or flagged. 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 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13470 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 package is not shown to contain malicious install-time or covert behavior, but it exposes a concrete runtime shell-injection vulnerability through normal media processing.
Independent scan evidence
public snapshot- lib/Utils/messages-media.js builds an ffmpeg shell command by interpolating a media file path, then calls child_process.exec.
- The video-thumbnail path reaches that helper from lib/Utils/messages.js; a caller-supplied local video path can reach the shell.
- This is a runtime command-injection/RCE risk, though no covert payload or exfiltration was found.
- package.json preinstall only runs engine-requirements.js, which checks Node's major version and exits on unsupported versions.
- No eval/vm/dynamic remote-code loader, credential harvesting, or AI-agent configuration mutation was found.
- Network code implements WhatsApp Web/media operations and explicit version checks, not install-time callbacks.
- lib/index.js only clears the console and prints package branding at import time.
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to ynastore-baileys@1.0.21.
The versions list below shows the verdict for each recorded version.
- Avoid installing ynastore-baileys@1.0.21. 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.