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 (f961ec09baa139430fb2b04c3fef5350f16f659c8de585787a26f3c8535fca38)
package.json declares the `libsignal` dependency as `github:tenka-san/libsignal-node`, a non-registry source pointing at a personal GitHub account with no tag or commit SHA. On `npm install`, npm fetches whatever the default branch's HEAD points to at that moment and runs any lifecycle scripts inside the cloned repo, so the owner of that account controls code that executes on the installer's machine. The account is unrelated to the upstream Baileys/libsignal publishers, and the package's own metadata is inconsistent (homepage and repository fields point at a Telegram URL while the bug tracker points at a different GitHub org, `pou-code/Baileys`), which is consistent with a repackaged Baileys lure rather than a legitimate fork.