risk-detection

Details

---
_-= Per source details. Do not edit below this line.=-_

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

## Source: ghsa-malware (a5cca5d23bae017227475832b4b03b5233d8c9fe360892d77b6e7ed54129680b)
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.

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.