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 (18526e44113025f1e08a31eb237515c63ae912a6cfe82bec37c14895f4f23178)
package.json declares its sole dependency `ltidisafe` as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.2.tgz) rather than a registry version range. On `npm install`, npm fetches that tarball with no version pin, no integrity hash, and no registry provenance, then installs it and runs any lifecycle scripts it contains on the installer's machine. The shipped index.js is an inert stub (exports {}), so the manifest's off-registry fetch is the only functional effect of installing this package. The dependency host is unrelated to the publishing scope `@futurae-public`, and the implausibly high version (99.9.1) is consistent with a dependency-confusion shape intended to win resolution over an internal package of the same name. Whoever controls the tarball URL controls code executed on every installer.
Source: ghsa-malware (83c42a14c04ce9fcb5d9a0961256e32f46c22dc4760a782adb65a76cb11adf4d)
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.