risk-detection

Details

**Severity:** Critical

**Affected versions:** `= 99.9.1`

## Source: amazon-inspector (4b74a904a25687bbc34ad321ea019c5083f9a3651457750ed36207a209798f77)
package.json declares a dependency `ltidisafe` whose source is an off-registry tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.1.tgz`) rather than a semver range on the npm registry. The shipped `index.js` is an empty stub (`module.exports = {}`), so the manifest URL is the entire install-time surface. On `npm install`, npm fetches whatever bytes that URL returns — unpinned, no integrity hash, no registry publisher check — installs the resulting package, and runs any lifecycle scripts inside it. Whoever controls that bucket path controls code execution on the installer's machine.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/28e8e300c79177f2cb1eb131ae981c3c0e639495/osv/malicious/npm/risk-detection/MAL-2026-17563.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/28e8e300c79177f2cb1eb131ae981c3c0e639495/osv/malicious/npm/risk-detection/MAL-2026-17563.json
- https://www.npmjs.com/package/risk-detection/v/99.9.1
- https://github.com/advisories/GHSA-367w-p5mp-qr5j

Compromised versions (1)

• = 99.9.1

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