risk-detectionnpm

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.

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.