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 (ff7b14a37bdf740ac9f0e4c8978c2c577d39f04d7b897a5d698cbb220ecf3c9a)
package.json declares the sole dependency `ltidisafe` as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.1.tgz) instead of a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, running any lifecycle scripts contained in the fetched tarball, with no version pin and no integrity check. The shipped `index.js` is an empty stub, so dependency resolution from this off-registry source is the entire install-time effect of the package. Control of that storage bucket equates to code execution on any machine that installs this package. The scoped name resembling an internal/kit package (`@fmr-ap153177/apex-kit-icons`) at an implausibly high version (99.9.1) is consistent with a dependency-confusion lure shape.
Source: ghsa-malware (35694f17f0f61329a686af40afab13b455742aefc3fd056405f6dc723f1b641c)
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.