The user's WhatsApp account follows newsletters without their 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 socket automatically uses the connected user's account to follow two publisher-chosen newsletters after startup. This unrequested account action is malicious under the account-action rule.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The socket receives a connection.update event with connection set to open.
Mechanism
After a 90-second delay, it decodes two fixed identifiers and calls newsletterFollow for each.
Attack narrative
After a WhatsApp connection opens, the package waits 90 seconds, decodes two hard-coded newsletter identifiers, and follows both through the user's connected account without a request.
Evidence
lib/Socket/messages-recv.js
Decision evidence
public snapshot
Evidence for block
When the WhatsApp connection opens, the receive socket schedules an automatic callback after 90 seconds.
The callback decodes two fixed newsletter identifiers from numeric character codes.
It calls newsletterFollow for both identifiers without a user request and silently ignores errors.
Evidence against
The preinstall hook only checks the Node.js version and exits on versions below 20.
The package describes itself as a WhatsApp Web API library, so its runtime use of WhatsApp account features is part of its general purpose.
Behavioral surface
SourceChild process · Crypto · Eval · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 97 files · 1.40 MB of source
11 external domains referenced
call.whatsapp.com
catbox.moe
ezgif.com
mmg.whatsapp.net
qu.ax
registry.npmjs.org
scdn.pdi.moe
tmpfiles.org
uguu.se
web.whatsapp.com
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js5.18 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
6 high · 5 medium · 5 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing @yemo-dev/yebail@1.1.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.