Recipients receive publisher-selected attribution that the caller did not request, promoting the publisher through the user's WhatsApp account.
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 event-message send path silently inserts a hard-coded publisher newsletter attribution and relays it to recipients. This is an unrequested account action that promotes the publisher through the user's WhatsApp account.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A caller uses the socket's sendMessage method with event-message content.
Mechanism
The event handler inserts a fixed newsletter name and JID into message context, then relays the modified message.
Attack narrative
When a caller sends an event message through the normal `sendMessage` API, the package adds the hard-coded `shenvn.` newsletter attribution and JID to the event context, then relays the altered message to the requested recipient. This promotes the publisher's channel through the user's WhatsApp account without a request to include it.
Evidence
lib/Socket/messages-send.jslib/Socket/dugong.js
Network endpoints1
120363297591152843@newsletter
Decision evidence
public snapshot
Evidence for block
The exported socket API exposes `sendMessage(jid, content, options)` as the normal message-sending method.
When content is an event message, `sendMessage` routes it to `handleEvent`.
`handleEvent` inserts the hard-coded newsletter attribution `shenvn.` and JID `120363297591152843@newsletter` into the outgoing event message.
The handler relays that message to the requested JID, so the attribution reaches recipients without an explicit request to include it.
Evidence against
The preinstall script only checks the Node.js major version and exits on versions below 20.
The package is a WhatsApp socket library, and the suspicious attribution is limited to event messages rather than added on import.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @zetagoaurum-socket/wasocket@3.2.7. 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.