Which versions of sc-geeksquad-core are malicious?

The following npm versions of sc-geeksquad-core are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate sc-geeksquad-core if I installed it?

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.

I already installed sc-geeksquad-core — how do I know if it already compromised me?

If sc-geeksquad-core 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.

Is sc-geeksquad-core part of a known attack campaign?

Yes — sc-geeksquad-core is associated with the IN-MAL-2026-014891 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sc-geeksquad-core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sc-geeksquad-core (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-geeksquad-core across your stack and pipelines.

Malicious package

sc-geeksquad-corenpm

sc-geeksquad-core is a confirmed malicious npm package (MAL-2026-12435) 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-geeksquad-core (npm)

MAL-2026-12435

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sc-geeksquad-core

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.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

2fd2458d8a5843f57187868a2c244a376dd3d2daef420d3c564c775ef6a2782a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sc-geeksquad-core (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-geeksquad-core across your stack and pipelines.
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 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-geeksquad-core 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

No. sc-geeksquad-core on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014891

References

npmjs.com

Credits

Amazon Inspector · 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database