Which versions of graphnetworkx are malicious?

The following npm versions of graphnetworkx are flagged malicious: 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.10, 2.1.11. Treat any of these as compromised.

How do I remediate graphnetworkx if I installed it?

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.

I already installed graphnetworkx — how do I know if it already compromised me?

If graphnetworkx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is graphnetworkx part of a known attack campaign?

Yes — graphnetworkx is associated with the RLMA-2025-04549, RLUA-2025-05027, RLUA-2026-01964 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 graphnetworkx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for graphnetworkx (6 malicious versions).

Malicious package

graphnetworkxnpm

Advisory published Aug 14, 2025Updated Apr 16, 2026

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

Find it
Search your lockfiles and build artifacts for graphnetworkx (6 malicious versions).
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.
Did it already run?
If graphnetworkx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

reversinglabs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database