The user's account is made to follow newsletters 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 package silently follows hard-coded WhatsApp newsletters when its normal socket is constructed. This is an unrequested account action toward targets chosen by the publisher, which meets the malicious account-actions rule.
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
When the normal message socket is constructed; follow requests are scheduled after a delay.
Mechanism
The newsletter socket sends WhatsApp `FOLLOW` queries to publisher-selected newsletter IDs and suppresses errors.
Attack narrative
Constructing the package's normal message socket creates a newsletter socket that schedules follow requests to hard-coded newsletter IDs. This uses the user's WhatsApp account for publisher-chosen account actions without an explicit request.
The newsletter socket schedules `FOLLOW` queries to hard-coded newsletter accounts without a caller-provided target.
Normal message-socket construction invokes the newsletter socket, triggering those scheduled actions.
Evidence against
The package is a WhatsApp API library, so WhatsApp network operations fit its stated purpose; the automatic follows of publisher-chosen targets do not.
The preinstall script only checks the Node.js version.
Behavioral surface
SourceChild process · Crypto · Eval · Filesystem · Network · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency
Scanned 93 files · 1.34 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.js8.08 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
6 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 malvin-wa@0.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.