Which versions of graphsync are malicious?

The following PyPI versions of graphsync are flagged malicious: 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate graphsync if I installed it?

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

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

Yes — graphsync 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 graphsync across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for graphsync (2 malicious versions).

Malicious package

graphsyncPyPI

Advisory published Dec 9, 2025Updated Feb 11, 2026

graphsync is a confirmed malicious PyPI package (MAL-2025-192385) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphsync (PyPI)

MAL-2025-192385

Immediate action

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

pip uninstall graphsync

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

2 flagged

1.1.01.1.1

Indicators of compromise (SHA-256)

dbb10327d6553750848c2b849abba1ed717438928a6cfdc148b73de73db8e9db

5f90028620c243d8f4c4345f3d9de2b21c0d1fcc6a7b56d7654589baa760f39f

ec94d3fbe5a41c721fdb8f6de0b7485d5b8a13e61f65f72a7e0754c7f5589ae6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for graphsync (2 malicious versions).
If you installed it — respond
graphsync 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 graphsync 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. graphsync on PyPI has been identified as a malicious package (versions 1.1.0, 1.1.1 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 graphsync-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

Explore

All malware advisories How O3 detects malware Vulnerability database