If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (0e08146748974a55b50e565bc0ae7fc1788c9b8a28858536c697505032334310)
On `npm install`, the package's `preinstall` script runs `node callback.js`, which collects `os.hostname()`, `os.userInfo().username`, `process.cwd()`, `npm_config_registry`, and multiple CI repository-slug environment variables (GITHUB_REPOSITORY, CI_PROJECT_PATH, BUILD_REPOSITORY_NAME, and similar) and sends them as query-string parameters in an HTTP GET to the hardcoded endpoint `http://75.119.137.232:31337/depconfuse`. The package is published at version `9999.0.0` with a generic description and the exfil path is literally `/depconfuse`, matching the dependency-confusion reconnaissance pattern: publish a very-high-version squat of an internal-sounding name to the public registry so private builds that misresolve pick it up and identify themselves to the attacker. Installer identity, working directory, internal registry URL, and internal repository slugs leave the host to an attacker-controlled bare-IP endpoint at install time, enabling targeted follow-on supply-chain intrusion against the affected organization.