Malicious code in sc-wizard (npm)

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

Source: amazon-inspector (b6626c24ff3f61de611b5962b6a1b21a5f694dfb32059e31f956875dc9d1db02)

package.json declares the package's only dependency ltidisafe as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.1.tgz) rather than a registry version range. On npm install, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts contained in the fetched tarball — unpinned, integrity-unchecked, and outside the npm registry's publish controls. The shipped index.js is an empty stub, so the manifest-declared off-registry URL is effectively the entire install-time payload. The dependency source is a mutable third-party storage bucket; whoever controls that URL controls code running on the installer's machine at install time. The high version number (99.9.1) relative to a short, generic name is consistent with a dependency-confusion lure intended to win resolution against an internal sc-wizard package.

Source: ossf-package-analysis (54691cc130e614ee031186f7e646c3e6076efad6105a6e9cad68f62aa736516b)

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

It is considered malicious because:

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