Uses the user's WhatsApp account to follow a channel selected by the package publisher.
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 a hard-coded WhatsApp newsletter after socket creation, using the user's authenticated account. This unsolicited publisher-directed account action is malicious.
Static reason
One or more suspicious static signals were detected.
Trigger
Application creates the package's message socket; the follow request is scheduled for 90 seconds later.
Mechanism
The newsletter socket sends a WhatsApp newsletter FOLLOW query for the hard-coded newsletter ID, without a user request.
Attack narrative
When an application creates the message socket, the package creates its newsletter socket and schedules a follow request for a fixed WhatsApp newsletter 90 seconds later. This uses the user's authenticated WhatsApp session to take an account action toward a publisher-selected target without the user's request.
Creating the message socket creates a newsletter socket, which schedules a follow request to the hard-coded target 120363400725985615@newsletter after 90 seconds.
The fixed-target follow request uses the WhatsApp newsletter FOLLOW action.
Evidence against
The preinstall script only checks the Node.js version and exits if it is below 20.
The scanner-flagged API-key-like string appears among protocol token strings in lib/WABinary/constants.js.
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.34 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
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.1.5. 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.