Malicious code in fanarena-common (npm)

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

Source: amazon-inspector (e0da88f07c843cff93266258d7d4e30c369b05fb52974170e25abb1e6c33e3c5)

package.json declares a dependency ltidisafe sourced directly from the bare HTTPS URL https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.8.tgz rather than from the npm registry. On npm install, npm fetches and installs whatever bytes that URL returns, with no registry-side integrity check, no version resolution, and no publisher binding — and executes any lifecycle scripts contained in the fetched tarball. The host is unrelated to any declared repository or homepage for this package, and the implausibly high package version (99.9.1) is consistent with a dependency-confusion / forced-resolution shape against an internal package of the same fanarena-* family. The manifest alone is the attack surface: regardless of the current contents of the remote tarball, the publisher of that URL can change the bytes installers execute at any time.

Source: ossf-package-analysis (d81686cb5b877d15810946a299ba819a875a3304e45d65a3fdb83c5473ac664b)

The OpenSSF Package Analysis project identified 'fanarena-common' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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