The user’s WhatsApp account is made to follow a channel they did not choose.
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 default socket construction path schedules an authenticated follow of a hard-coded WhatsApp channel without a user request. This is an unrequested account action toward a publisher-chosen target, so the package is malicious.
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
A consumer creates the package’s default socket; the follow is scheduled for 120 seconds later.
Mechanism
The newsletter socket sends a FOLLOW query for the hard-coded channel ID 120363329486691279@newsletter.
Attack narrative
Creating the public socket factory constructs a newsletter socket that schedules a WhatsApp FOLLOW query for the publisher-chosen channel ID after two minutes, without asking the user.
When a newsletter socket is created, it schedules a follow of the hard-coded WhatsApp channel 120363329486691279@newsletter after 120 seconds, without a user request.
The public makeWASocket factory reaches this code through the default socket construction chain.
The preinstall script only checks that Node.js is version 20 or newer.
Evidence against
The package’s declared purpose is a WhatsApp library, so ordinary WhatsApp network activity is expected; the hard-coded channel follow is not required by that purpose.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 101 files · 1.78 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 · 4 medium · 6 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing nishiki-bail@1.1.1. 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.