lilys-baileys
Whatsapp baileys coded by Fallzx-Coderid.
This report shows the evidence for lilys-baileys@1.3.3. 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 23d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17398 confirms this npm version as malicious.
Advisory
MAL-2026-17398
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in lilys-baileys (npm)
Details
This package is part of a large family (100+ identified as of September 2026) of near-identical forks of the Baileys WhatsApp Web library that inject a covert channel-subscription action into the WhatsApp socket layer. On connect, the injected code issues an authenticated `w:mex` FOLLOW query (query_id 7871414976211147) against one or more attacker-chosen WhatsApp Channel/Newsletter JIDs, using the installer's own authenticated WhatsApp session -- silently subscribing the victim's account to channels it never asked to join.
The target JID(s) are hidden from casual source review via one of several obfuscation techniques observed across the family: a plain string literal, base64 encoding, base64+XOR, or a char-code array reconstructed at runtime. Some variants instead fetch a mutable, attacker-controlled remote JSON/JS list of target JIDs from GitHub or another host at runtime, letting the target list change after installation without a new npm publish. Every sample in the family shares the same underlying mechanism (a wrapped/patched socket-connect routine that fires the FOLLOW query some seconds after connect), even though the package name, JID value(s), and obfuscation/delivery method differ per fork.
The malicious action abuses the installer's own authenticated WhatsApp session to gain reach and subscribers for attacker-controlled channels; it does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
Affected package: lilys-baileys (npm), version(s): 1.3.3, 1.3.2.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The shell-injection primitive is concrete and reachable through an exported media helper, so this package contains a critical vulnerability. Static inspection did not establish deliberate malware behavior or data exfiltration.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Calling the thumbnail helper with untrusted path, time, size, or destination values.
Impact
Arbitrary commands can run with the privileges of the application process.
Mechanism
Unsafely interpolated arguments passed to a shell through exec.
AI rationale
The shell-injection primitive is concrete and reachable through an exported media helper, so this package contains a critical vulnerability. Static inspection did not establish deliberate malware behavior or data exfiltration.
Evidence
lib/Utils/messages-media.jspackage.json
Independent scan evidence
public snapshotAI called this Suspicious at 93.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for AI warning decision
- The exported media helper builds a shell command by interpolating its arguments and executes it with exec.
- An attacker able to control the thumbnail path, timestamp, or dimensions can inject shell syntax into that command.
- The preinstall hook invokes engine-requirements.js, but that file is absent from the package snapshot.
- Importing the main entry point prints unsolicited terminal output.
Evidence against
- The network and file operations inspected implement WhatsApp media upload, download, encryption, and temporary-file handling.
- No credential harvesting, unrelated exfiltration endpoint, or persistence code was found in the inspected sources.
Behavioral surface
ChildProcessCryptoFilesystemNetworkWebSocket
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 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 unpkgWAProto/index.jsView file
•path = WAProto/index.js
kind = oversized_source_file
sizeBytes = 8472622
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkglib/Defaults/baileys-version.jsonView file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 2
High
Findings
3 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedlib/Defaults/baileys-version.json
HighKnown Malware Source Similaritylib/Utils/messages-media.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to lilys-baileys@1.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing lilys-baileys@1.3.3. 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.