sentrykitnpm

package.json declares a self-referential dependency where the key sentrykit maps to the bare HTTPS URL https://repo.securityctrl.com/sentrykit instead of a registry version range. On npm install, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts contained in the fetched artifact. The source is unpinned, integrity-unchecked, and not the official npm registry; the shipped package body is a one-line stub, so the manifest itself is the entire delivery mechanism. The dependency key equals the package's own name and the version constraint (30.0.0) is implausibly high for a package of this size, matching the dependency-confusion smuggling shape where a high version number is used to win resolution against an internal package of the same name. 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.