Malicious code in @fcsmc/commercial-analytics (npm)

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

Source: amazon-inspector (bdca5cebb5734d25233e8016eb494ab6ec1a099899f0814fc846e46ad351582c)

The package ships an inert index.js stub but declares its sole dependency ltidisafe as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.8.tgz) in package.json rather than a registry version range. On npm install, npm fetches and installs whatever bytes that URL returns, including any lifecycle scripts contained in the fetched tarball, bypassing npm registry version pinning and integrity controls. The scoped package name under @fcsmc with no README, no description, and an empty main is consistent with a dependency-confusion lure whose only on-install effect is to resolve attacker-controlled code from a third-party storage bucket.

Source: ossf-package-analysis (2a6c1e570c16bbf3b94ecc31e622c4d31be7c8575c90eaffc238ca1ef36e659d)

The OpenSSF Package Analysis project identified '@fcsmc/commercial-analytics' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

• The package communicates with a domain associated with malicious activity.