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 (e582d9d611f75576135d06bf83cf71b60a58fbbf475ba61e656bf190a73c5546)
The package ships only an empty stub (index.js exports {}) and a manifest whose sole dependency, `ltidisafe`, is declared as a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.9.tgz) rather than a registry version range. On `npm install`, npm fetches whatever bytes that URL serves — unpinned, with no integrity hash, from a bucket outside the npm registry — and runs any lifecycle scripts contained in that tarball on the installer's machine. The scope `@fmr-ap149494`, the implausibly high version `99.9.1`, and the `depenconf` path segment together match the dependency-confusion shape used to win resolution against an internal package name of the same identifier.
Source: ghsa-malware (b57013da538b75a1d29bb4635d576e0b30103b1698823638fe4f6f59dde3b0b7)
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 (e3505d2eebf31d1938862b6f6744d353fadaf980b9a27860f2a7c36d863828b9)
The OpenSSF Package Analysis project identified '@fmr-ap149494/apex-base-component' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.