@finzzcloud/baileys
Websocket Whatsapp API for Node.js
This report shows the evidence for @finzzcloud/baileys@1.0.0, the only known version.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package follows remotely selected WhatsApp newsletters using the user's authenticated account by default after socket setup. This is an unrequested account action, so the package is malicious.
Static reason
One or more suspicious static signals were detected.
Trigger
Creating the socket and logging in; the action runs after a delay unless BAILEYS_AUTO_FOLLOW is set to "off".
Impact
Uses the user's account to follow channels without an explicit request; the remote list can choose the targets.
Mechanism
Fetches newsletter IDs from a hard-coded FinzzCloud endpoint or an environment override, then sends a FOLLOW action for each valid ID through the authenticated WhatsApp socket.
Attack narrative
When the newsletter socket is created and a WhatsApp account is logged in, the package fetches a list of channels from a FinzzCloud endpoint and follows each returned newsletter through that account. This unsolicited account action is enabled by default; the opt-out environment variable does not make it user-requested.
AI rationale
The package follows remotely selected WhatsApp newsletters using the user's authenticated account by default after socket setup. This is an unrequested account action, so the package is malicious.
Evidence
lib/Utils/messages-media.jslib/Socket/newsletter.jslib/Socket/messages-send.js
Network endpoints1
ch-finzzcloud.vercel.app/lyyn
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Newsletter socket setup calls loadBase automatically; auto-follow is enabled by default unless BAILEYS_AUTO_FOLLOW is set to "off".
- loadBase fetches a newsletter list from https://ch-finzzcloud.vercel.app/lyyn, or from the BAILEYS_CH_LIST_URL override.
- For each returned newsletter ID, loadBase calls the WhatsApp newsletter query with the FOLLOW action.
- The newsletter query sends through the socket's WhatsApp query function.
Evidence against
- The package describes itself as a WhatsApp WebSocket API, so its normal use involves authenticated WhatsApp connections.
- The newsletter-follow code waits for a logged-in account ID before acting.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggedlib/WABinary/constants.jsView file
601patternName = google_api_key
severity = high
line = 601
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L601601patternName = google_api_key
severity = high
line = 601
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L601lib/Socket/builder.jsView file
10if (!mod) {
L11: try { mod = (await import(name)).default ?? (await import(name)); }
L12: catch { throw new Error(`Modul "${name}" belum terpasang. Jalankan: npm i ${name}`); }
Medium
Dynamic Require
Package source references dynamic require/import behavior.
lib/Socket/builder.jsFindings
5 High7 Medium5 Low
HighHigh Secretlib/WABinary/constants.js
HighBase64 Obscured Urllib/Utils/messages-media.js
HighNode Builtin Dependency Squatpackage.json
HighSemantic Analysis LimitedWAProto/index.js
HighSecret Patternlib/WABinary/constants.js
MediumDynamic Requirelib/Socket/builder.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
LowScripts Present
LowWeak Cryptolib/Utils/crypto.js
Affected versions and remediation
This report applies to @finzzcloud/baileys@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @finzzcloud/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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.