Malicious code in bytepack-probe-a7x3 (npm)

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.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1f158536e9d84e6cee18e2a3ce84869e34f1564ec18a1313a9e8c03b304e3d70) package.json declares a dependency `leak-internal` whose source is the HTTPS tarball URL https://src-ssrf.bytedance.net/ssrf/probe.tgz rather than a registry version range. On `npm install`, npm fetches and installs whatever bytes that URL currently returns, executing any lifecycle scripts contained in the fetched tarball. There is no version pin, no integrity hash, and no signature check, so the code executed on the installer's machine is whatever the operator of that host serves at the moment of install. The hostname suggests an SSRF-probe artifact hosted on an internal-looking domain, and the dependency name `leak-internal` together with the path segment `ssrf/probe.tgz` indicates the fetched payload is intended to run probing behavior inside the installer's network.

Source published

21 Sep 2026 19:51:34 UTC

Source modified

21 Sep 2026 20:30:13 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.