bytepack-probe-a7x3

Details

**Severity:** Critical

**Affected versions:** `= 1.0.0`

## 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.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/8b22724c6b21215e1887acbd30e4ea6c5cef5d35/osv/malicious/npm/bytepack-probe-a7x3/MAL-2026-16364.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/8b22724c6b21215e1887acbd30e4ea6c5cef5d35/osv/malicious/npm/bytepack-probe-a7x3/MAL-2026-16364.json
- https://www.npmjs.com/package/bytepack-probe-a7x3/v/1.0.0
- https://www.npmjs.com/package/bytepack-probe-a7x3/v/1.0.1
- https://github.com/advisories/GHSA-pjjj-2389-rwj6

Compromised versions (1)

• = 1.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.