librastandardlibnpm

package.json at line 11 declares a dependency whose key equals the package's own name (librastandardlib) and whose value is an off-registry HTTPS URL (https://repo.securityctrl.com/librastandardlib) instead of a registry version range. On npm install, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, running any lifecycle scripts inside with no version pin and no integrity check. The implausibly high version (45.0.0) and the self-referential dependency name are consistent with a dependency-confusion shape designed to win resolution against an internal package. The shipped index.js is an inert stub, so the manifest URL is the entire delivery mechanism — whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time.

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.