Uses the user's WhatsApp account to follow publisher-selected channels without consent and can undo the user's unfollows.
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 ordinary socket creation path silently follows channels supplied by a hard-coded remote file using the user's authenticated WhatsApp account. The repeated task can undo user unfollows, making this an unrequested account action.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Creating the normal messages socket; the follow task starts automatically.
Mechanism
Fetches channel IDs from a hard-coded GitHub raw URL, follows each ID, then repeats the process every five minutes.
Attack narrative
When the standard messages socket is constructed, it creates the newsletter socket and launches an automatic task. That task downloads channel IDs from a hard-coded GitHub file and follows each one with the user's WhatsApp credentials. It repeats every five minutes, so it can restore follows the user removes. These account actions are unrelated to an explicit user request.
Creating the messages socket constructs the newsletter socket, which starts an auto-follow task without a user request.
The task fetches channel IDs from https://raw.githubusercontent.com/Zacky-Tzy/ChBail/main/ch.json and follows each ID using the authenticated WhatsApp socket.
The task starts immediately and repeats every five minutes, restoring follows if the user removes them.
Evidence against
The package preinstall script only checks the Node.js major version and exits on unsupported versions.
The package is presented as a WhatsApp socket library, so ordinary WhatsApp network access serves its purpose.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @zetagoaurum-socket/wasocket@2.1.1. 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.