Users' WhatsApp accounts may follow the publisher's newsletter without their request; verifier keys and owner names are disclosed to the bot operator.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The socket automatically follows a publisher-chosen WhatsApp newsletter when the connection opens, without a user request. The exported verifier also reports supplied keys and owner names to a hard-coded Telegram bot.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Creating a WhatsApp socket and opening its connection triggers the follow guard; calling the exported verifikasi function triggers Telegram reporting.
Mechanism
The socket follows a publisher-selected newsletter JID with retries and a recurring timer. The verifier posts supplied keys and owner names through a hard-coded Telegram bot token and chat ID.
Attack narrative
When the WhatsApp connection opens, the socket code automatically follows a hard-coded newsletter selected by the publisher, then retries periodically. Separately, the exported verifier sends the supplied key and owner name to a hard-coded Telegram bot on verification success or failure. The automatic account action is unrelated to ordinary WhatsApp API operation and is sufficient to classify the package as malicious.
Evidence
lib/Socket/messages-send.jslib/index.js
Network endpoints2
api.telegram.org
raw.githubusercontent.com
Decision evidence
public snapshot
Evidence for block
When the WhatsApp connection opens, the library starts a follow guard that follows the hard-coded newsletter JID and retries periodically.
The exported verifier sends its supplied userKey and ownerName to a hard-coded Telegram bot.
The verifier reports both failed and successful keys to that bot.
Evidence against
The package describes itself as a WhatsApp Web API library, and its socket code handles WhatsApp connections.
The preinstall script only checks the installed Node.js version.
Behavioral surface
SourceChild process · Crypto · Eval · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 94 files · 1.35 MB of source
14 external domains referenced
api.telegram.org
call.whatsapp.com
catbox.moe
ezgif.com
mmg.whatsapp.net
qu.ax
raw.githubusercontent.com
registry.npmjs.org
scdn.pdi.moe
tmpfiles.org
uguu.se
web.whatsapp.com
wppconnect.io
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js8.08 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
2 critical · 8 high · 5 medium · 6 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing bellacloudy@26.3.14. 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.