katal-loggernpm

package.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/katal-logger) instead of a registry version range. On npm install, npm fetches whatever bytes that URL currently returns and installs them as the package, executing any lifecycle scripts contained inside. There is no version pin, no integrity/hash check, and the host is unrelated to the npm registry, so control over repo.securityctrl.com equates to code execution on the installing machine. The dependency key equals the package's own name (dependency-confusion shape) and the shipped index.js is an inert stub, so the manifest line is the entire delivery mechanism — the absence of scripts in this tarball does not mitigate the fetch.

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.