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 (26b3f1a7acd55a1642c9615fe72871781a6c0d6bea6f9d31aa42c700aa799704)
Package ships an empty module (index.js = 'module.exports = {};') under a name that resembles internal tooling, published at an inflated version 99.9.1 — the canonical shape used to win version resolution against a private-registry package of the same name. Its single dependency, 'ltidisafe', is declared not as a registry package but as a direct tarball URL on a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.2.tgz). On `npm install`, npm fetches that tarball from a location the registry does not audit and executes any lifecycle scripts and main module it contains. The path segment 'depenconf' and the version-inflation pattern are consistent with a targeted dependency-confusion attack. The lure package itself is hollow; the harm arrives through the URL-pinned transitive dependency.
Source: ghsa-malware (a0be9e59ec7bf82d86d83b2e882e979023b90460cc02b4fb109c7603f312daae)
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.