Changes the user’s WhatsApp account by subscribing it to a target chosen by the package publisher 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 uses the connected WhatsApp account to follow a hard-coded newsletter selected by the publisher. This is an unauthorized account action triggered by normal connection startup.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A connection made through the package’s normal socket stack reaches the open state.
Mechanism
A connection listener checks the hard-coded newsletter ID and sends a WhatsApp FOLLOW query when the account is not already following it.
Attack narrative
When a user’s WhatsApp connection opens, the package checks whether the account follows newsletter 120363394395254196@newsletter. If not, it sends a FOLLOW query for that fixed target. The normal socket construction path includes this listener, so the account action occurs without the user requesting a follow.
On an open connection, the newsletter socket checks a fixed newsletter and sends a FOLLOW query if the account is not already following it.
The fixed target is 120363394395254196@newsletter, and the newsletter socket is created by the package’s message socket layer used by its normal socket stack.
Evidence against
Behavioral surface
SourceCrypto · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 116 files · 1.92 MB of source
6 external domains referenced
call.whatsapp.com
mmg.whatsapp.net
raw.githubusercontent.com
web.whatsapp.com
wppconnect.io
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js4.27 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
9 high · 5 medium · 4 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing astrabail@1.0.9. 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.