ux-metrics-client-interaction-subscribernpm

package.json line 11 declares a dependency whose key equals the package's own name (ux-metrics-client-interaction-subscriber) and whose value is a bare HTTPS URL to a non-registry host: https://repo.securityctrl.com/ux-metrics-client-interaction-subscriber. On npm install, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts contained in it, with no version pin, no integrity hash, and no signature check. The shipped index.js is an inert stub, so the manifest itself is the entire delivery mechanism: control of repo.securityctrl.com equals code execution on the installer's machine. The self-name dependency-confusion shape (dependency key equals the package's own name, implausibly high version 45.0.0) is consistent with an attempt to win resolution against an internal package of the same name.

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.