sc-payment-utils
This report shows the evidence for sc-payment-utils@9999.0.0, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12801 confirms this npm version as malicious.
Advisory
MAL-2026-12801
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in sc-payment-utils (npm)
Details
sc-payment-utils@9999.0.0 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to sc-payment-utils@9999.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing sc-payment-utils@9999.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.