Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in nx-app (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-15516

Published

--- _-= 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.

Source published
28 Aug 2026 23:11:23 UTC
Source modified
24 Sep 2026 09:40:34 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 12 Nov 15:26 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current