calcite-webnpm

package.json at line 11 declares the package's own name as a dependency whose source is the bare URL https://repo.securityctrl.com/calcite-web instead of a registry version range. On npm install, npm fetches whatever tarball that URL returns and installs it with no version pin and no integrity check, executing any lifecycle scripts inside the fetched artifact. The shipped index.js is an inert stub, so the manifest itself is the entire install-time payload, and whoever controls repo.securityctrl.com controls code that runs on every installer. The dependency key equals the package's own name (dependency-confusion shape), and the implausibly high version (45.0.0) is consistent with an override attempting 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.