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

graphfluxnpm

graphflux is a confirmed malicious npm package (MAL-2025-47927) that executes malicious code on install (malicious versions 0.0.1, 0.0.1-beta, 0.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphflux (npm)

MAL-2025-47927
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall graphflux

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

10 flagged
0.0.10.0.1-beta0.0.20.0.30.0.40.0.50.0.60.0.70.0.80.0.9

Indicators of compromise (SHA-256)

81407cede8c4a0a29787867b0a52b7947864a775ff7efbe05ce00785ea6160a0
bf0e378c2828a110a49ad48a2a7ddd0fb27f03764985d1c2140cbc00e877750e
0a7c829e26871a5af54e27ac3e13890c7c46eb8bbf1f7d00a1d738c5af73467e
83585384bca53d7ecc0d57b5dbd5695be3bf5eeb82e6593bbcfbbf6a651ed64b
369ac1689c9db060c512c935229c6a674ddc2d1dc321c0524052b796bbdf8452

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 graphflux (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphflux across your stack and pipelines.

  2. If you installed it — respond

    Remove graphflux 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 graphflux 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 graphflux 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. graphflux on npm has been identified as a malicious package (versions 0.0.1, 0.0.1-beta, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w9vj-gxp2-cmfmRLMA-2025-05383RLUA-2025-05806RLUA-2025-06359RLUA-2026-01959

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks graphflux-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

graphflux (npm) malicious package — MAL-2025-47927 | O3 Security