framework-zeronpm

package.json line 11 declares a dependency whose source is the bare HTTPS URL https://repo.securityctrl.com/framework-zero instead of a registry version range. On npm install this URL is fetched and installed, running any lifecycle scripts in the returned tarball, with no version pin and no integrity check. The dependency key equals the package's own name (framework-zero), a dependency-confusion shape where the manifest itself is the delivery mechanism, and the pinned version 45.0.0 is implausibly high for the name — consistent with a resolution-winning squat against an internal package. The host repo.securityctrl.com is unrelated to any npm registry and can serve arbitrary content that changes at any time after publish.

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.