rubbydev-crash-baileys
This report shows the evidence for rubbydev-crash-baileys@1.0.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.0-stage, 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/OSVOpenSSF/OSV advisory MAL-2026-17450 confirms this npm version as malicious.
Advisory
MAL-2026-17450
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in rubbydev-crash-baileys (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-70 (cited line 68: `QueryIds.FOLLOW`) run in the body of `makeNewsletterSocket`, so they fire whenever a socket is created: 10 seconds later the code sends a FOLLOW query for the channel JID `120363427594836299@newsletter`, stored as the base64 literal `MTIwMzYzNDI3NTk0ODM2Mjk5QG5ld3NsZXR0ZXI=` and decoded with `Buffer.from(..., "base64")`. 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: `6f864bd56ccace95160247ff88e51a463a7655ce0daa083ac6748c714970e016`.
References
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
Inspected lifecycle scripts, entrypoints, and high-signal files: preinstall is a Node 20 check, and network, ffmpeg, and token-dictionary hits match a Baileys WhatsApp client. Crash-themed naming and extra album protobuf fields are user-invoked dual-use messaging, not an install-time attack.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
npm install runs the Node version check; the host app must import the library and connect a socket.
Impact
No confirmed host compromise, credential theft, or unconsented install-time mutation was found. Scanner similarity and crash branding are naming and dual-use client features, not a supply-chain payload.
Mechanism
unofficial WhatsApp Web protocol client
AI rationale
Inspected lifecycle scripts, entrypoints, and high-signal files: preinstall is a Node 20 check, and network, ffmpeg, and token-dictionary hits match a Baileys WhatsApp client. Crash-themed naming and extra album protobuf fields are user-invoked dual-use messaging, not an install-time attack.
Independent scan evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- package.json preinstall only runs node ./engine-requirements.js; prepare and prepack are empty.
- engine-requirements.js only checks that Node.js is version 20 or newer and exits if not.
- lib/WABinary/constants.js lists password as a WhatsApp binary protocol token, not a stored secret.
- lib/Utils/business.js parses WhatsApp product catalog nodes.
- lib/Utils/messages-media.js uses child_process.exec only to run ffmpeg for a video thumbnail.
- Network use is WhatsApp hosts plus a public WhiskeySockets Baileys version fetch.
Evidence against
- The package name is rubbydev-crash-baileys and the README links t.me/RubbyCrashXComunity.
- lib/Socket/luxu.js album send injects extra forwarding and newsletter protobuf fields.
- dependencies include libsignal from github:tenka-san/libsignal-node.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/WABinary/constants.jsView file
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Findings
5 High4 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis Limitedlib/Utils/business.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to rubbydev-crash-baileys@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing rubbydev-crash-baileys@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.