Uses the user's authenticated account to perform follows they did not 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 two hard-coded newsletters after a WhatsApp connection opens, using the user's authenticated account without a request. This is a concrete unsolicited account action and warrants blocking.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A WhatsApp connection opens; the action is scheduled after 90 seconds.
Mechanism
The receive socket decodes two newsletter IDs from numeric character arrays and calls newsletterFollow for each.
Attack narrative
When a WhatsApp connection opens, the receive socket schedules a delayed callback that reconstructs two hard-coded newsletter IDs and calls newsletterFollow for both. That method sends follow queries through the authenticated WhatsApp socket, causing unsolicited account actions toward targets selected by the package publisher.
When the WhatsApp connection opens, a delayed callback decodes hard-coded newsletter IDs and calls newsletterFollow on them.
newsletterFollow sends a follow query for the supplied newsletter ID, so the automatic calls use the account's WhatsApp connection to follow publisher-chosen targets.
Evidence against
The preinstall script only checks the Node.js major version and exits when it is below 20.
Behavioral surface
SourceChild process · Crypto · Eval · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 299 files · 1.43 MB of source
12 external domains referenced
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
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js10.1 MB file, sampled 256 KB
High entropy strings
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@3.0.4. 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.