amplitude-experiment

Details

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

## 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 [email protected] 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.

Compromised versions (1)

• 55.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.