Which versions of graphalgo are malicious?

The following PyPI versions of graphalgo are flagged malicious: 3.5.1rc0.dev0, 3.5.2, 3.5.3, 3.5.5, 3.5.6. Treat any of these as compromised.

How do I remediate graphalgo if I installed it?

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

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

Yes — graphalgo is associated with the RLMA-2025-03605 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 graphalgo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for graphalgo (5 malicious versions).

Malicious package

graphalgoPyPI

graphalgo is a confirmed malicious PyPI package (MAL-2025-6514) that executes malicious code on install (malicious versions 3.5.1rc0.dev0, 3.5.2, 3.5.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in graphalgo (PyPI)

MAL-2025-6514

Immediate action

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

pip uninstall graphalgo

Malicious versions

5 flagged

3.5.1rc0.dev03.5.23.5.33.5.53.5.6

Indicators of compromise (SHA-256)

5849fb6a13f382e8b3728dd072ba85726018ee7a20a01ae609c24a621415891b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for graphalgo (5 malicious versions).
If you installed it — respond
Remove graphalgo 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 graphalgo 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. graphalgo on PyPI has been identified as a malicious package (versions 3.5.1rc0.dev0, 3.5.2, 3.5.3, 3.5.5, 3.5.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03605

Credits

ReversingLabs · finder

Detect & block this

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