This report shows the evidence for @yemo-dev/yebail@4.2.12. 44 of 44 known versions are blocked or flagged.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-18919 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-18919 confirms this npm version as malicious.
Advisory
MAL-2026-18919
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @yemo-dev/yebail (npm)
Details
@yemo-dev/yebail is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own WhatsApp account to WhatsApp Channels chosen by the publisher. When the socket connects, code in lib/Socket/messages-recv.js sends the WhatsApp w:mex FOLLOW query for the channel ID(s) 120363408975923153@newsletter, 120363421171049265@newsletter (stored as character-code arrays), using the victim's authenticated session and without telling them. Same behaviour as the PhantomSub family (MAL-2026-17342).
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package’s preinstall hook only checks the Node.js version and exits if it is below 20. Network access and temporary dependency installation belong to an explicitly invoked WhatsApp protocol maintenance script, and the inspected entry point shows no unrelated import-time behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Install runs the Node.js version check; network fetching and temporary parser installation occur only when the maintenance helper is invoked.
Impact
No unauthorized data collection, credential transmission, or unrelated file modification was identified.
Mechanism
The preinstall script checks the Node.js major version. The maintenance helper fetches WhatsApp Web data from web.whatsapp.com and can install temporary Acorn parser dependencies for protocol updates.
AI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall hook only runs engine-requirements.js, which checks the Node.js major version and exits on versions below 20.
The package entry point re-exports the library’s socket, utilities, types and protocol modules; no unrelated install or collection behavior appears in the entry-point code.
The update helper fetches WhatsApp Web data and installs temporary parser dependencies when the user explicitly runs its maintenance command.
The inspected protobufjs postinstall creates its CLI node_modules directory and checks dependency version compatibility.
Evidence against
The manifest does define a preinstall hook, but its target is only the Node.js version check.
The update helper contains network access and package installation, but it is a maintenance script rather than a lifecycle hook or import-time action.
The flagged constant strings are WhatsApp protocol dictionary tokens; no credential or secret transmission was identified.
Behavioral surface
SourceChild process · Crypto · Dynamic require · Eval · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 337 files · 1.66 MB of source
12 external domains referenced
call.whatsapp.com
catbox.moe
ezgif.com
mmg.whatsapp.net
qu.ax
raw.githubusercontent.com
registry.npmjs.org
scdn.pdi.moe
tmpfiles.org
uguu.se
web.whatsapp.com
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js10.1 MB file, sampled 256 KB
High entropy strings
Findings
5 high · 6 medium · 5 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
The versions list below shows the verdict for each recorded version.
Avoid installing @yemo-dev/yebail@4.2.12. 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.