integration-amplitude

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (dcd9ffdf0c07f64af4034ec76aea284a6290f4633f2c80eefa65579c1a297bfb)
package.json declares the package's own name as a dependency whose source is the bare HTTPS URL https://repo.securityctrl.com/integration-amplitude rather than a registry version range. On npm install, npm fetches whatever bytes that host serves and installs them, executing any lifecycle scripts contained inside, with no version pin and no integrity check. The shipped index.js is a 3-line stub, so this manifest line is the sole install-time code path. The dependency key matching the package's own name is the dependency-confusion shape, and the implausibly high version (45.0.0) is consistent with an attempt to win resolution against an internal package of the same name. Whoever controls repo.securityctrl.com controls code executed on the installer's machine.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/integration-amplitude/MAL-2026-15510.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/integration-amplitude/MAL-2026-15510.json
- https://www.npmjs.com/package/integration-amplitude/v/45.0.0
- https://github.com/advisories/GHSA-9vjx-7728-3xp4

Compromised versions (1)

• = 45.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.