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 (110901fcd2d59ab6eed44d962da05830610e5c3cb03ca103db5a379e6c6052e4)
package.json declares a single dependency whose key equals the package's own name (`amplitude-experiment`) and whose source is the bare HTTPS URL `https://repo.securityctrl.com/amplitude-experiment` instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, with no version pin and no integrity check, running any lifecycle scripts contained in the fetched tarball. The shipped source of amplitude-experiment@55.0.0 itself is an inert stub, so the manifest line is the entire delivery mechanism. The dependency key matching the package's own name mirrors a dependency-confusion shape against the legitimate `amplitude-experiment` name, and the implausibly high version (55.0.0) is consistent with a resolution-winning squat.
Source: ghsa-malware (1de763ed35499a4b3ce864ee6f4120ef872a3f1dd5837fffd8ae2930e6ce6ac7)
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.