An unrequested account action subscribes the user's WhatsApp account to the chosen newsletter.
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 a follow request to a fixed WhatsApp newsletter without user consent. This is an unrequested account action toward a publisher-chosen target.
Static reason
One or more suspicious static signals were detected.
Trigger
Constructing the standard WhatsApp socket; the action is scheduled 90 seconds later.
Mechanism
A timed callback sends a newsletter query using the FOLLOW query ID and a hard-coded newsletter target; errors are suppressed.
Attack narrative
Creating the standard socket reaches the newsletter socket builder, which schedules a FOLLOW request for the hard-coded WhatsApp newsletter after 90 seconds. The request runs without an explicit user action and suppresses errors, causing an unsolicited subscription through the user's account.
The normal makeWASocket construction path reaches makeNewsletterSocket through the registration, business, message-receive, and message-send socket builders.
makeNewsletterSocket schedules a query 90 seconds later that uses QueryIds.FOLLOW for the hard-coded target 120363400725985615@newsletter, and silently catches errors.
Evidence against
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestGit dependency · No license · Wildcard dependency
Scanned 97 files · 1.33 MB of source
4 external domains referenced
raw.githubusercontent.com
v.whatsapp.net
web.whatsapp.com
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js8.00 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
1 critical · 4 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 amiudmodz@5.0.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.