nx-app

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (8671a9b563cebe9de36365a80edc1f242be492933cadb3e45ea590c8c5e1e115)
package.json declares its own name `nx-app` as a dependency whose value is a raw HTTPS URL (`https://repo.securityctrl.com/nx-app`) rather than a semver range against the npm registry. On `npm install`, npm fetches a tarball from that URL and runs any lifecycle scripts it contains, with no version pin, no integrity hash, and no signature check. Whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency key (matching the package's own name) is a dependency-confusion shape that forces resolution to the off-registry URL even when a registry-hosted `nx-app` exists, and the shipped in-tree source is an inert stub so the manifest URL is the sole payload delivery vector.

## Source: ghsa-malware (6c7af1fac9e695388df59eb95fd3170fedc1b9ae8a282f9de84d5259aea78f82)
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.

Compromised versions (1)

• 9999.0.0-security-test

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.