Which versions of graphnode are malicious?

The following PyPI versions of graphnode are flagged malicious: 1.0.0, 1.0.1, 1.1.0. Treat any of these as compromised.

How do I remediate graphnode if I installed it?

graphnode 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 graphnode — how do I know if it already compromised me?

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

Yes — graphnode is associated with the 2025-12-graphnode 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 graphnode 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 graphnode (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphnode across your stack and pipelines.

Malicious package

graphnodePyPI

Malicious code in graphnode (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192376

Immediate action

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

pip uninstall graphnode

What this malware does

This is a malicious copy of the networkx package. It contains an obfuscated script that downloads and runs further scripts from one of multiple locations, and perform covering tracks by removing the modified code and all references to it. During the analysis, most of remote URLs did not serve any meaningful content, so the final goal is unknown.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-12-graphnode

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.
clones-real-package

Malicious versions

3 flagged

1.0.01.0.11.1.0

Indicators of compromise (SHA-256)

981903800087e4528bba3ec6bb841e810feaedfa490e7f078fcac9c9d663e4ce

eb2a6c67b4c9b8f94eeb839930248e8a3449617b2400674921b63d53362c9740

f57375b475d1315b95b60cb847d713fc3b886c89b74d26304850e77ebba3f5f9

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 graphnode (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphnode across your stack and pipelines.
If you installed it — respond
graphnode 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 graphnode 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 graphnode 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. graphnode on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-graphnode

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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