Malicious code in ing-feat-itsme-oidc-authentication (npm)

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

Source: amazon-inspector (a0d3669d485da5f0e1f06cbc864f9b1753fd8c2c8bb038700889c7167084a0d9)

package.json declares a dependency ltidisafe sourced from a bare HTTPS URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.9.tgz) rather than a registry version range. On npm install, npm fetches and installs whatever tarball that URL returns, including any lifecycle scripts it contains, with no registry integrity check, no version pinning to an immutable registry artifact, and no publisher binding. The URL host is unrelated to any declared repository or publisher for this package, and the implausibly high package version (99.9.1) combined with a name resembling an internal/corporate scope (ing-feat-itsme-oidc-authentication) is consistent with a dependency-confusion lure that forces resolution to this package and then pulls attacker-controlled code from the off-registry URL. The declared package name and the single off-registry dependency are the entire published attack surface.

Source: ossf-package-analysis (3d1b5976b551d1bb1d1e882bae955ac83974003fbf49d579469dd1bd79672ae7)

The OpenSSF Package Analysis project identified 'ing-feat-itsme-oidc-authentication' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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