sc-geeksquad-corenpm
Advisory published Updated
sc-geeksquad-core is a confirmed malicious npm package (MAL-2026-12435) that steals credentials and exfiltrates sensitive data (malicious versions 99.9.1, 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sc-geeksquad-core (npm)
What this malware does
[email protected] declares a preinstall script node callback.js that runs automatically on npm install. The script collects the installer's hostname (os.hostname()), OS username (os.userInfo().username), current working directory (process.cwd()), configured npm registry (npm_config_registry), and a set 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), then sends them via HTTP GET to the hardcoded bare-IP endpoint http://75.119.137.232:31337/depconfuse as query parameters. The placeholder version 9999.0.0 combined with a generic scoped-sounding name is the canonical dependency-confusion reconnaissance shape: the package is published to public npm to intercept internal-package name resolution and beacon back which private-namespace builds are vulnerable to substitution.
The OpenSSF Package Analysis project identified 'sc-geeksquad-core' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for sc-geeksquad-core (2 malicious versions).
If you installed it — respond
sc-geeksquad-core 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-geeksquad-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks sc-geeksquad-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.