The user's WhatsApp account joins the selected newsletters without a request from the user.
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 socket automatically follows two hard-coded newsletters after connection, an account action toward targets selected by the package publisher. This is malicious even though 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; previous stored version diff introduced dangerous source
Trigger
The socket emits connection.update with connection set to open; the action runs after a 90-second delay.
Mechanism
The code decodes two hard-coded newsletter identifiers and invokes sock.newsletterFollow for each, without user input or consent.
Attack narrative
After a WhatsApp connection opens, the package waits 90 seconds, reconstructs two hard-coded newsletter IDs from character codes, and follows both through the authenticated socket. This uses the user's account to join publisher-selected targets without a user request.
Evidence
lib/Socket/messages-recv.js
Decision evidence
public snapshot
Evidence for block
When the WhatsApp connection opens, a 90-second timer decodes two hard-coded newsletter identifiers and calls newsletterFollow for both.
The preinstall hook only runs a Node.js version check and exits on versions below 20.
The added media upload helper sends its input buffer to third-party file hosting services when called.
Evidence against
The package describes itself as a WhatsApp Web API library, and its main entry point exports the socket API.
The media uploads occur inside an explicit helper, rather than automatically at import or install.
Avoid installing @yemo-dev/yebail@4.0.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.