sc-payment-utilsnpm
sc-payment-utils is a confirmed malicious npm package (MAL-2026-12801) that steals credentials and exfiltrates sensitive data (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sc-payment-utils (npm)
What this malware does
[email protected] declares a preinstall script that executes callback.js on npm install. The script collects host identity (os.hostname(), os.userInfo().username), the current working directory, the configured npm registry, and a battery of CI repository-slug environment variables (GITHUB_REPOSITORY, CI_PROJECT_PATH, BUILD_REPOSITORY_NAME, BITBUCKET_REPO_FULL_NAME, TRAVIS_REPO_SLUG, DRONE_REPO, BUILDKITE_PIPELINE_SLUG, CIRCLE_PROJECT_REPONAME, JOB_NAME), and issues an HTTP GET to a hardcoded bare-IP endpoint at http://75.119.137.232:31337/depconfuse with those fields as query parameters. The 9999.0.0 version number and beacon shape are consistent with a dependency-confusion reconnaissance callback targeting internal package names leaked into public registry resolution.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sc-payment-utils (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sc-payment-utils across your stack and pipelines.
If you installed it — respond
sc-payment-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If sc-payment-utils was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sc-payment-utils before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sc-payment-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.