registry / Malware / @developmentyora/baileyss

@developmentyora/baileyss

This report shows the evidence for @developmentyora/baileyss@1.0.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 21d ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-17439 confirms this npm version as malicious.

Advisory

MAL-2026-17439

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in @developmentyora/baileyss (npm)

Details

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp `w:mex` FOLLOW query (query_id 7871414976211147) for each target channel JID. `package/lib/Socket/newsletter.js` lines 62-103 (cited line 68: `QueryIds.FOLLOW`) run in the body of `makeNewsletterSocket`, so they fire whenever a socket is created: 90 seconds later, and then at 5-second intervals, the code sends FOLLOW queries for four channel JIDs, each stored as a base64 literal decoded with `Buffer.from(..., "base64")`: `120363427594836299@newsletter`, `120363425875407481@newsletter`, `120363407288464467@newsletter` and `120363426218991285@newsletter`. There is no opt-out and the behavior is not documented. Line numbers refer to version 1.0.0. Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in `engine-requirements.js`), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers. SHA-256 of the published npm tarball(s): 1.0.0: `dcd91e2ea65ee271b729b118e7778cce1e028d90527c3b330aa04c59456dcba6`.

References

OpenSSF/OSV advisory ARTICLE PACKAGE

Source & flagged code

0 flagged

No flagged code excerpts are attached to this scan.

Source & flagged code

0 flagged · loading source

No flagged code excerpts are attached to this scan.

Findings

1 High

HighOsv Malicious Advisory

Affected versions and remediation

This report applies to @developmentyora/baileyss@1.0.0.

The versions list below shows the verdict for each recorded version.

Avoid installing @developmentyora/baileyss@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: 2026-10-02 05:30:05.345Z (UTC).

Source advisory published: 2026-10-01 23:05:37.000Z (UTC).

This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

3 known versions

0.0.1-securitylatestUnknown—AllowUnder ReviewOct 16, 2026, 1:08 AM 0.0.0-stageClean—AllowPublishedOct 16, 2026, 1:08 AM 1.0.0shownMaliciousMalwareBlockPublishedAug 21, 2026, 3:38 PM

OpenSSF/OSV Malicious Advisory

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Source & flagged code

Related packages

Other malware packages