The connected account is made to follow a publisher-chosen newsletter without an explicit user request.
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 socket setup automatically follows a hard-coded WhatsApp newsletter after 90 seconds. This uses the user's account for an action toward a publisher-chosen target without their request, so the package is malicious.
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
Creating the normal makeWASocket stack; the follow is sent 90 seconds after newsletter socket construction.
Mechanism
An automatic timer submits a FOLLOW query for the hard-coded newsletter ID over the package's WhatsApp connection.
Attack narrative
When a user creates the package's normal WhatsApp socket, the constructor chain creates a newsletter socket. That socket schedules a FOLLOW query 90 seconds later for the hard-coded newsletter 120363303045895814@newsletter, making the connected account follow a target selected by the publisher.
The exported makeWASocket builds the registration, business, receive, and message socket layers; creating the message socket also creates a newsletter socket.
Newsletter socket creation schedules a timer that sends a FOLLOW action to the hard-coded target 120363303045895814@newsletter after 90 seconds.
The follow request is sent through the WhatsApp query mechanism, so normal socket use triggers an account action toward a publisher-chosen target without the user's request.
Evidence against
The preinstall script only checks the Node.js major version and exits on versions below 20.
The action uses the package's WhatsApp connection and does not show credential or file exfiltration.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing patron-pro@2.1.5. 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.