Malicious code in @ecg-internal/js-react-i18n (npm)

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.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (533583f613bf03556a1660b5bd8eaf4d5899c96dc79f4c42ae6b883aea8fde0e) The package is published under an internal-looking scope (@ecg-internal) and ships a stub main module that returns a Proxy of no-op functions for every property access — it provides none of the i18n functionality its name implies. Its only real behavior is firing beacon.cjs, which executes both from the declared postinstall lifecycle script (`node beacon.cjs`) and from a top-level `require('./beacon.cjs').fire()` in the main module. beacon.cjs collects the installer's hostname (via `os.hostname()`), install path (`__dirname`), current working directory, Node.js version, and package name, and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not a publisher-aligned domain and the shape — internal-looking scope + hollow functional surface + install- and import-time callback with host identifiers to a bare IP — is a dependency-confusion reconnaissance probe designed to identify internal build systems that resolve the private name from the public registry. ## Source: ghsa-malware (4b6637975491d2cb9a6fe062dab13216afeeeda88e533e8cfde6d628df841bf5) 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

23 Oct 2026 02:01:46 UTC

Source modified

23 Oct 2026 02:45:04 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.