A WebSockets library for interacting with WhatsApp Web
Blocked & quarantined
The user's WhatsApp account follows a channel without an explicit request.
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 package automatically follows a hard-coded WhatsApp newsletter when its connection opens, using the user's authenticated account. This is an unrequested account action toward a publisher-selected target.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
The user creates a newsletter socket and its WhatsApp connection opens.
Mechanism
A connection event handler calls the newsletter follow query with a hard-coded channel ID.
Attack narrative
When the WhatsApp connection opens, the newsletter socket automatically sends a follow query for a hard-coded channel ID. This uses the user's authenticated WhatsApp connection to perform an account action toward a target chosen by the package publisher, without an explicit request from the user.
Evidence
lib/Socket/newsletter.js
Network endpoints1
WhatsApp newsletter service
Decision evidence
public snapshot
Evidence for block
When the WhatsApp connection opens, the newsletter socket automatically follows a hard-coded channel using the authenticated connection.
Evidence against
The preinstall script only checks the Node.js major version and exits if it is below 20.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 107 files · 1.77 MB of source
5 external domains referenced
call.whatsapp.com
raw.githubusercontent.com
wa.me
web.whatsapp.com
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js4.23 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
7 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 wertybailz@1.0.10. 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.