Which versions of pylibcugraph are malicious?

The following PyPI versions of pylibcugraph are flagged malicious: 0.0.0, 0.0.1. Treat any of these as compromised.

How do I remediate pylibcugraph if I installed it?

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

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

Yes — pylibcugraph is associated with the GENERIC-standard-pypi-install-pentest, RLMA-2025-06582, RLUA-2026-00639 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 pylibcugraph 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 pylibcugraph (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pylibcugraph across your stack and pipelines.

Malicious package

pylibcugraphPyPI

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

MAL-2025-191835

Immediate action

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

pip uninstall pylibcugraph

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

0.0.00.0.1

Indicators of compromise (SHA-256)

cf23321de2d06a1a0109252f4894fb300640d819be364aeb1880ae09e74fad7a

b298ab8786b687f39d3ce25f6a69effd415c27b384fa23bc45c5fdf640448105

2132074866be3b0e9a4a92d159654af1e6b97f427f1cb45259f916ad3aef545a

1a0d75e196940b5d863e4cdb2df26955a426752d42059b1f0ea46d4647e8da13

a0568a38f912f1444b13261227a46e893d6e45b90cafc6261086dcf4ea07f844

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

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2025-06582RLUA-2026-00639

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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