Uses the user’s WhatsApp account to perform an unrequested action toward a publisher-chosen target.
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 normal messages-socket setup schedules an authenticated WhatsApp FOLLOW action toward a hard-coded newsletter, without user consent. This is malicious account abuse; the preinstall hook itself only checks the Node.js version.
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 application creates its messages socket; the follow request is scheduled for 90 seconds later.
Mechanism
makeNewsletterSocket schedules a WhatsApp w:mex FOLLOW query for 120363408522985879@newsletter.
Attack narrative
When an application creates the package’s messages socket, it also creates a newsletter socket. That socket schedules a FOLLOW query for 90 seconds later, targeting the hard-coded newsletter 120363408522985879@newsletter. The request uses the authenticated WhatsApp connection, so the package performs an account action toward the publisher’s chosen target without a user request.
WhatsApp server (w:mex query; destination supplied as S_WHATSAPP_NET)
Decision evidence
public snapshot
Evidence for block
Creating the messages socket creates the newsletter socket as part of normal socket setup.
Newsletter socket creation schedules a FOLLOW query after 90 seconds for the hard-coded newsletter ID 120363408522985879@newsletter.
The query is sent through WhatsApp’s w:mex protocol using the authenticated socket, so the package follows the publisher-chosen newsletter without the user requesting it.
Evidence against
The preinstall script only checks the Node.js major version and exits if it is below 20.
The media and message utilities’ network and process APIs are consistent with WhatsApp media handling and are not evidence of the account action.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing zenvyflump@2.0.3. 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.