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 (23bc43e71e1158fc102445f53b3880fe32a99bb6a8557b99d1b17279e8f41f44)
package.json declares `libsignal` as `github:chatunitycenter/libsignal-node` with no commit SHA, tag, or integrity hash. On `npm install`, npm clones the default-branch HEAD of that repository and installs whatever it returns, including executing any lifecycle scripts (preinstall/install/postinstall/prepare) present in the cloned source. The resolved bytes are mutable: whoever controls the `chatunitycenter/libsignal-node` repository can push new commits at any time and those commits will run on every installer that resolves this dependency going forward. The dependency key resembles the well-known `libsignal-node` project but points to an account-controlled fork rather than a registry version range or a pinned commit, so the installer cannot audit or reproduce what will be fetched.
Source: ghsa-malware (52978b0c3293c9df936b51c70527efeb5b0f496a59f0df857016fc781f876043)
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.