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 yangming708 (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-13845

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f670e6c07175c9534c5554cc89c44a73a22d46a18a9a19140030b5b446fba17f) The tarball contains only package.json and index.html. package.json declares main: "index.html", which is not a requirable Node module, and no preinstall/install/postinstall/prepare lifecycle scripts are declared. index.html contains an obfuscated script (wrapped in a fake Cloudflare 'Just a moment...' template) that, if opened in a browser, decodes an encoded string and calls window.location.replace to redirect to the resulting URL. Because npm install does not execute HTML and require()/import cannot load this main, installing or loading the package does not execute any code on a developer or build machine. The artifact looks like registry spam / a browser-side redirect page mispublished as an npm package, not a supply-chain attack against installers. ## Source: ghsa-malware (3c66586cb4455acd4f9845b0ac788de86f9814180ee81055925867864db2ca7f) 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
12 Aug 2026 10:29:52 UTC
Source modified
12 Aug 2026 13:00:25 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 22 Nov 05:58 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current