Malicious code in @chatest/baileys (npm)

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

Source: amazon-inspector (f9c6f7960bb0d0edc97cac2310f15f01156a4dbc0b19e8ba8e4a42075882dc01)

The package.json of @chatest/[email protected] declares the libsignal dependency as github:chatunitycenter/libsignal-node with no commit SHA, tag, or semver pin. On npm install, this resolves to whatever bytes are at the default branch HEAD of that external GitHub repository at the moment of installation, including any lifecycle scripts contained in them. The dependency is actively consumed via require("libsignal") in lib/Signal/libsignal.js, so it is part of the runtime tree and loaded on module import as well. Whoever controls the referenced GitHub repository controls code that runs on every installer's machine, unpinned and integrity-unchecked. The package also exhibits a scope/branding mismatch: it is published as @chatest/baileys but its homepage and repository.url both point at @chatunity/baileys, and the README banner brands the module as ChatUnity Baileys.

Source: ghsa-malware (fe80b7b76923a24948c1d095c3dc2474c0aac3574a3cf2046bf152c7dcde0aac)

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.