Recipients may see the event as associated with the publisher's newsletter, using the user's account to promote a target the user did not select.
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 injects a hard-coded publisher-selected newsletter attribution into outbound EVENT messages, causing the user's account to promote a target they did not choose. The install 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
Trigger
A caller sends content detected as EVENT through sendMessage.
Mechanism
The event handler inserts forwardedNewsletterMessageInfo with a hard-coded newsletter name and ID before relaying the message to the caller's recipient.
Attack narrative
When an application using the package sends an EVENT message, the send path calls a handler that inserts fixed forwarded-newsletter attribution for newsletter ID 120363421563597486@newsletter, then relays that message to the caller's recipient. This covertly promotes the publisher-selected newsletter through the user's account; the behavior is triggered by sending an event, not by installation or import.
Evidence
lib/Socket/messages-send.jslib/Socket/damnn.js
Decision evidence
public snapshot
Evidence for block
The preinstall hook runs only a Node.js version check.
sendMessage receives its destination and content from the caller.
The EVENT branch adds fixed newsletter attribution to the outbound message, including publisher-selected newsletter ID 120363421563597486@newsletter.
Evidence against
The fixed attribution is added only when a caller sends content detected as an EVENT; it does not send a message during import or socket startup.
The preinstall hook does not contact a network or access project data.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @zephkiel/wbails@2.0.9. 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.