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 (35fe912c705e73aff92ef85fb3de7bf49ebaf1bd6e5736b963aeb1bcd66c2a0b)
package.json declares the sole dependency 'ltidisafe' as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.4.tgz) rather than a registry version range, with no integrity hash and no version pin. The shipped index.js is an empty stub, so the manifest is the entire published surface: on `npm install`, the tarball at that URL is fetched and installed, and any lifecycle scripts inside it execute on the installer's machine. Whoever controls that bucket path controls the code that runs. The package name 'library-shell' and scope '@library-wide' do not correspond to any functional code in the tarball, consistent with a lure whose only purpose is to pull in the off-registry dependency.
Source: ghsa-malware (08ae76e41cbd6797f41f2858531cfadd13b6122ff07a219e43097d467f52b13a)
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.
Source: ossf-package-analysis (40f52e7af5c6b8f0c78b5100b561b799fc6acd9fa9c5372982a14bb5c1b42da1)
The OpenSSF Package Analysis project identified '@library-wide/library-shell' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.