Which versions of grafeno-payments are malicious?

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

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

grafeno-payments is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

grafeno-paymentsnpm

grafeno-payments is a confirmed malicious npm package (MAL-2026-15572) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in grafeno-payments (npm)

MAL-2026-15572

Immediate action

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

npm uninstall grafeno-payments

What this malware does

On npm install, package.json's preinstall hook (node preinstall.js || true) auto-runs a script that (1) enumerates process.env for keys matching AWS|TOKEN|KEY|SECRET|PASS|API, concatenates them with the machine's hostname and username, base64-encodes the blob, and exfiltrates it via curl GET to http://216.126.236.46/r.php over plain HTTP; and (2) on non-Windows hosts invokes bash -i with a /dev/tcp redirection to 216.126.236.46:4444, giving the remote endpoint an interactive shell on the installer's machine. The || true suffix suppresses errors so npm install reports success while the payload runs. The package's stated payments purpose is a cover story; the shipped preinstall behavior is credential theft plus full-host remote code execution against the installer.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7af58da84956e51749cbb96923f12264cfdee76456b5010b526599b7da2c0caa

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for grafeno-payments (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-payments across your stack and pipelines.
If you installed it — respond
grafeno-payments is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If grafeno-payments 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-payments 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-payments 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-019150

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database