@fmr-ap149494/apex-base-component

Details

---
_-= Per source details. Do not edit below this line.=-_

## 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: 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.

Compromised versions (1)

• 99.9.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.