Malicious code in zeroz-baileys (npm)

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (7be2199641fd598bfa6c6a11fac2567fa0c50f3f55ae3a8e8cd9ecd6ec4bf20f)

[email protected] appears to be a fork of the Baileys WhatsApp library. A static pattern matched on keyword co-occurrence in lib/Utils/messages-media.js (require('child_process'), https.request, hostname, POST) within a single file. This shape is expected for a media-handling utility in a WhatsApp library (media upload/download via HTTPS requests, optional native tool dispatch). Traced-code corroboration of installer-side harm was not established — no specific installer secret is named as read, and no non-first-party attacker-controlled destination is identified. Being a fork of a widely-used library, the package warrants human review to confirm whether the fork introduces covert behavior (e.g., using the installer's WhatsApp session for author-controlled actions) versus being a legitimate derivative.

Source: ghsa-malware (55c04838c571c7688a361345f76683eefc0e7b1da6719b53cef0285f55b7f99b)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.