Malicious code in sc-font-icons (npm)

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

Source: amazon-inspector (1b8c91edd839dd00f2e58ad9296742f8c3c5ff126523bbd8ed7561fef7c8516e)

The package's preinstall script runs automatically on npm install and collects installer-side identifiers — os.hostname(), os.userInfo().username, process.cwd(), the configured npm registry, and CI repository slugs from GITHUB_REPOSITORY / CI_PROJECT_PATH — and sends them over plain HTTP GET to a hardcoded bare-IP endpoint at http://75.119.137.232:31337/depconfuse as query parameters. The version number (9999.0.0) and the beacon path (/depconfuse) are consistent with a dependency-confusion probe: the artifact exists to be pulled into internal builds that mis-resolve a private package name to the public registry, and to report back the internal package name, host, user, working directory, private registry URL, and repository slug of any environment that installs it. The destination is a bare IP with no TLS, unrelated to any legitimate npm publishing infrastructure, and the collected fields disclose internal repository and infrastructure naming to a third party.

Source: ossf-package-analysis (1b1e3d1dcd8af0ee16e8da5b321d8c532f9707503a36d90a8802b7835305fceb)

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

It is considered malicious because:

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