If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (3bcbf6493a6aa37ccc827723d6fd73b082c66d10a549af2413aba2a8a6f47b7f)
package.json for @bil-rgb/baileys@1.0.0 declares its `libsignal` dependency as `github:tenka-san/libsignal-node` with no commit SHA, no tag, and no integrity check. `npm install` resolves this value by cloning whatever currently exists at HEAD of that personal GitHub user's repository and running any lifecycle scripts contained in it. The resolution target is a personal user account unrelated to the upstream signalapp/libsignal-node or WhiskeySockets Baileys publisher, so the code that executes on an installer's machine at install time is whatever that account chooses to place in the referenced branch at the moment of install, independent of this package's own tarball contents. The remainder of the package body (lib/Utils/generics.js and surrounding files) is a Baileys fork; the install-time attacker control is produced by the manifest line itself.