Public mode

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

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 04:29 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in reactjs-risk (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-17339

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0e58c82916c5199ef9e73a5d70f91d120312151eb5c28090d8bbf6dbf4117543) The package's preinstall lifecycle script collects host identity metadata from the installer machine — os.hostname(), the output of `whoami`/os.userInfo().username, and os.platform() — hex-encodes the values, and issues a DNS A-record lookup for `<hex>.768hgkqn53abdemu8ikzkel4g.canarytokens.com`, causing the installer's hostname, username, and platform to be transmitted to the canarytoken operator on every `npm install`. The dns module is loaded via string concatenation (`'d'+'n'+'s'`) and the `whoami` command is similarly split, indicating deliberate obfuscation of the module and command names. The package's declared main entry is an empty stub with no library functionality, so the preinstall beacon is the package's only behavior. Installing this package auto-executes an unauthenticated exfiltration of installer identity metadata to a third-party DNS endpoint the installer did not opt into. ## Source: ossf-package-analysis (a32a318956967c92b753750e0b607e48db7eef07d05f25c2b687f3b9612f806e) The OpenSSF Package Analysis project identified 'reactjs-risk' @ 99.17.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Source published
30 Sep 2026 09:30:37 UTC
Source modified
30 Sep 2026 15:00:05 UTC
Observed 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

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 12 Nov 04:29 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current