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 ux-metrics-client-interaction-subscriber (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-15545

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6066e87b7b0822678d3514839bc7eba18d46ff1d034c12ea169f4c3513df132b) package.json line 11 declares a dependency whose key equals the package's own name (ux-metrics-client-interaction-subscriber) and whose value is a bare HTTPS URL to a non-registry host: https://repo.securityctrl.com/ux-metrics-client-interaction-subscriber. On npm install, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts contained in it, with no version pin, no integrity hash, and no signature check. The shipped index.js is an inert stub, so the manifest itself is the entire delivery mechanism: control of repo.securityctrl.com equals code execution on the installer's machine. The self-name dependency-confusion shape (dependency key equals the package's own name, implausibly high version 45.0.0) is consistent with an attempt to win resolution against an internal package of the same name. ## Source: ghsa-malware (8508ce9c4cb39fb152e59f1ccd62e92f910b37d8a7b4b25b8e62cc768886e1bc) 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:16:03 UTC
Source modified
24 Sep 2026 09:40:40 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 14:22 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current