analytics-web-clientnpm

package.json at line 11 declares a dependency whose key equals this package's own name (analytics-web-client) and whose source is a bare HTTPS URL (https://repo.securityctrl.com/analytics-web-client) rather than a registry version range. On npm install, npm fetches whatever bytes that host serves and runs any lifecycle scripts they contain, with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest line is the entire published surface: whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency name additionally matches the dependency-confusion shape, aimed at winning 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.