Malicious code in @xrelly-stack/bails (npm)

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

Source: amazon-inspector (195817f808f7604633cfab5e678aea8d4bb53f116c72605d9a2f0852834c5ae3)

package.json declares whatsapp-rust-bridge-baron as git+https://github.com/7ucg/whatsapp-rust-bridge.git — an unpinned git URL with no commit SHA and no tag. On npm install, npm fetches whatever the current HEAD of that repository returns and runs any lifecycle scripts inside it, with no integrity check and no version pinning. Whoever controls that GitHub repository controls install-time code execution on every machine that installs this package, and can change that code at any time without republishing to npm. The dependency name (-baron suffix) is also a sibling of the primary whatsapp-rust-bridge registry dependency listed alongside it, sourced entirely from a third-party GitHub account rather than the npm registry. Combined with the package's @xrelly-stack/bails scope resembling the Baileys WhatsApp library ecosystem, the manifest itself is the delivery vector regardless of the contents of the JavaScript shipped in the tarball.

Source: ghsa-malware (50a8bf97baef2afe279a36ada416d0c235247d68c31748c360ca9bf863cdbe49)

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.