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

graphnetworkxnpm

graphnetworkx is a confirmed malicious npm package (MAL-2025-21882) that executes malicious code on install (malicious versions 2.1.6, 2.1.7, 2.1.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphnetworkx (npm)

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

What this malware does

The package graphnetworkx was found to contain malicious code.

Malicious versions

6 flagged
2.1.62.1.72.1.82.1.92.1.102.1.11

Indicators of compromise (SHA-256)

50c06ef08dc76e72bdc78082ce89a830f60bfcf42fd9217d17b5622d732a3acd
12b124e4a03debd491edf59b6c4f40ae3a41fac5ef33689178ce4f80d55399ff
f27b5ce759d704d77e6c23e783e7700e8bcd0dbf2d54e822e817f3ae260c2298

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

  2. If you installed it — respond

    Remove graphnetworkx 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 graphnetworkx 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 graphnetworkx 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. graphnetworkx on npm has been identified as a malicious package (versions 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.10, 2.1.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04549RLUA-2025-05027RLUA-2026-01964

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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

graphnetworkx (npm) malicious package — MAL-2025-21882 | O3 Security