This report shows the evidence for yagami-bail@1.0.5, the only known version.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-19038 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-19038 confirms this npm version as malicious.
Advisory
MAL-2026-19038
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in yagami-bail (npm)
Details
yagami-bail 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/newsletter.js sends the WhatsApp w:mex FOLLOW query for the channel ID(s) 120363401467939056@newsletter (stored as base64 strings), 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 install hook only enforces the declared Node.js requirement. The fixed newsletter ID appears in metadata for an explicitly selected event-message send path, and the inspected code does not automatically act on that newsletter.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The preinstall hook checks the Node.js version; event-message handling runs when the caller sends an EVENT message.
Impact
No unauthorized account action, credential collection, or data exfiltration was identified.
Mechanism
The fixed newsletter ID appears as metadata on a caller-requested event message, not as a separate automatic newsletter action.
The versions list below shows the verdict for each recorded version.
Avoid installing yagami-bail@1.0.5. 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.