If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (7053eaf141232704108519a3b3e7a0f1197d9eaabfa9fd3f4ff56ae9f753d763)
package.json declares its sole dependency `ltidisafe` as a bare HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.3.tgz`) rather than a registry version range or a git ref pinned to a commit SHA. On `npm install`, npm fetches whatever bytes that URL currently returns and installs the resulting package, running any lifecycle scripts it contains. The tarball is unpinned, has no integrity hash, is not resolved through the npm registry, and the content at that URL can be swapped by whoever controls the storage bucket without any change to this package. The shipped `index.js` is an empty stub (`module.exports = {}`), so the off-registry dependency URL is effectively the entire payload delivered to installers. The dependency name does not correspond to a known npm package, and the storage.googleapis.com bucket is not an official registry endpoint.
Source: ghsa-malware (aace32b8168a6a561c371138c21441a17b7a0d68412df2aa2ac8f312498640df)
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.