integration-amplitudenpm

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.

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.