Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

grafeno-actionsnpm

grafeno-actions is a confirmed malicious npm package (MAL-2026-15596) that executes malicious code on install (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in grafeno-actions (npm)

MAL-2026-15596
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall grafeno-actions

What this malware does

The OpenSSF Package Analysis project identified 'grafeno-actions' @ 999.0.0 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
999.0.0

Indicators of compromise (SHA-256)

3a52df88a9094028961676cb72f9e43f88fcef959cc4e1db63687785058c2d7d

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for grafeno-actions (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging grafeno-actions across your stack and pipelines.

  2. If you installed it — respond

    Remove grafeno-actions 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.

  3. Did it already run?

    If grafeno-actions 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.

  4. How O3 protects you

    O3 blocks grafeno-actions 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-actions on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks grafeno-actions-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.

Explore

grafeno-actions (npm) malicious package — MAL-2026-15596 | O3 Security