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 axis-datagrid (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-15528

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0b8e97884917400dda89c79754629edd51961e893d64fa580de04bb82bd0cab3) package.json declares a dependency whose key equals the package's own name (`axis-datagrid`) and whose source is the bare HTTPS URL `https://repo.securityctrl.com/axis-datagrid` instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them, running any lifecycle scripts they contain, with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest itself is the entire install-time payload: whoever controls repo.securityctrl.com controls code executed on the installer's machine. The self-referential dependency name (dependency-confusion shape) and an implausibly high version (45.0.0) for a package whose actual code is a placeholder are consistent with a package designed to win resolution against an internal name and pull code from an off-registry host. ## Source: ghsa-malware (263c347ed52368ea52f9475207427612e53fd22d40d8ec0e11d43bff604df40b) 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:11 UTC
Source modified
24 Sep 2026 09:40:56 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