nx-appnpm
nx-app is a confirmed malicious npm package (MAL-2026-15516) that executes malicious code on install (malicious version 9999.0.0-security-test). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nx-app (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nx-app (version 9999.0.0-security-test). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nx-app across your stack and pipelines.
If you installed it — respond
Remove nx-app from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If nx-app was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nx-app before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks nx-app-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.