Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

spc-grafeno-loginnpm

Advisory published Updated

spc-grafeno-login is a confirmed malicious npm package (MAL-2026-15633) 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-grafeno-login (npm)

MAL-2026-15633
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall spc-grafeno-login

What this malware does

The package's preinstall.js lifecycle script auto-executes on npm install and performs two attacker-benefiting actions against the installer. First, it enumerates process.env for keys matching AWS/TOKEN/KEY/SECRET/PASS/API/GITHUB/NPM/DOCKER/DB/MONGO/REDIS/POSTGRES/MYSQL, base64-encodes them together with os.hostname(), os.userInfo().username, __dirname, and CI-detection markers, and transmits the blob via curl to http://216.126.236.46/r.php over plain HTTP. Second, on non-Windows hosts it spawns a reverse shell to 216.126.236.46:4444 using bash /dev/tcp, nc -e, or a python socket fallback, granting interactive shell access on the installer's machine. Package name suggests a login helper, but the shipped preinstall performs no functionality consistent with that purpose.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

01c074fc169a09169385a53a74ea0bc928f45bf20d40621d7c4b4657e28c01f2

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for spc-grafeno-login (version 1.0.0).

  2. If you installed it — respond

    spc-grafeno-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.

  3. Did it already run?

    If spc-grafeno-login 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

No. spc-grafeno-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-019304

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks spc-grafeno-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.

Explore

spc-grafeno-login (npm) malicious package — MAL-2026-15633 | O3 Security