Public mode

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

Some sources or documents need attention: 275/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 05:48 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in fetch-hash-cache-atomic (npm)

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

osv · MAL-2026-18340

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7fa5c13f5b907c79079d9030292f1a6dac9d2f0ced56c2efe0e1bfd7021acdb4) package.json declares its sole dependency as a direct HTTPS URL (https://artifacts.creditslib.com/npm/plugin-client-queue-field) rather than a registry version range, with no version pin and no integrity hash. On npm install, npm fetches whatever bytes that URL currently returns and installs them, executing any lifecycle scripts the fetched tarball contains. The shipped index.js is a one-line re-export of that dependency, so the manifest line is effectively the entire published surface of the package. The host artifacts.creditslib.com is unrelated to any registry or declared publisher, and the content it serves can be changed at any time without a package republish. ## Source: ghsa-malware (2fe31e64c3fbc62b9e89b7b27b225663277114a17af5c84b4ea75ec3de4ccc8f) 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
27 Oct 2026 15:49:52 UTC
Source modified
29 Oct 2026 14:45:06 UTC
Observed here
29 Oct 2026 15:12:22 UTC
Source terms
OSV · upstream source license applies

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

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

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 7 Nov 05:48 UTC · 275 of 275 readable · 274 fully read · documentation 469/469 current