Malicious code in localize-translate (npm)
Exploitation and risk
Source statusCISA 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-14279
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1a4a3b42b13a5ba692edd9761c2d32d6682f555828df49cb44e40b623861a1f0) On `npm install`, the package's postinstall lifecycle script collects installer host identifiers (hostname, platform, arch, node version, package name, timestamp, npm lifecycle event) and POSTs them as JSON to the hardcoded host gigww0v7.instances.poc.jchunt.top at path /localize-translate. The destination is a non-registry, author-controlled endpoint that the installer never opted into, and the beacon fires automatically at install time on every host that installs the package. The collected fields are limited to host identity (no credential, filesystem, or environment scraping is present), but the beacon is unconditional, undisclosed, and directed to a third-party host — the shape of an install-time reconnaissance callback rather than legitimate telemetry.
- Source published
- 19 Aug 2026 07:54:36 UTC
- Source modified
- 19 Aug 2026 08:34:48 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.