The user’s account sends content containing the publisher-selected newsletter attribution without a separate request to include it.
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 adds a hard-coded newsletter attribution to outgoing event messages and sends them through the user’s WhatsApp account. This is a publisher-serving account action on the feature’s send path.
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
A caller sends content detected as an EVENT through the package’s message-send path.
Mechanism
The event handler inserts the newsletter JID into forwarded newsletter metadata, then relays the message.
Attack narrative
When the caller sends an event message, the send path invokes `handleEvent`. That handler embeds the hard-coded newsletter JID in the outgoing message metadata and relays the message, adding publisher-selected attribution to the user’s content.
Evidence
lib/Socket/messages-send.jslib/Socket/dugong.js
Decision evidence
public snapshot
Evidence for block
The send path routes EVENT content to `rahmi.handleEvent`.
The event handler adds the hard-coded newsletter JID `120363297591152843@newsletter` to outgoing message metadata.
The handler relays the constructed message to the recipient.
Evidence against
The preinstall hook only checks the Node.js version and exits on versions below 20.
The newsletter attribution is added when the event-message feature is used, not on import or socket startup.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @zetagoaurum-socket/wasocket@2.2.2. 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.