Malicious code in @xatancchii/natabaileys (npm)

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

Source: amazon-inspector (262bd24b77d6bc63e4f9b139d3688b3956f85cd25b9b23613abc807841944578)

The package is a fork of Baileys published under @xatancchii that remaps the libsignal import to a third-party scoped package via "libsignal": "npm:@bellaxchuu/libsignal-node@latest" in package.json. The scope @bellaxchuu matches neither the publisher of this package (@xatancchii) nor the upstream project (WhiskeySockets/libsignal-node), and the version is pinned to the mutable @latest dist-tag with no integrity check. The aliased dependency supplies the Signal protocol crypto primitives and is loaded on every require of the package through lib/Signal/libsignal.js and lib/Utils/crypto.js (SessionCipher / SessionBuilder / SessionRecord paths). Each npm install fetches whatever @bellaxchuu/libsignal-node currently publishes under @latest, and that code is executed in-process whenever the Baileys fork is imported, including from inside session handling for WhatsApp Web connections where decrypted message plaintext and long-lived session keys are available.

Source: ghsa-malware (f5ae1bb8eedff775ab95af3b382114e74ca3097cf294a34db67087e99cabd900)

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.