Which versions of cugraph-service-server are malicious?

The following PyPI versions of cugraph-service-server are flagged malicious: 0.0.1, 23.12.0. Treat any of these as compromised.

How do I remediate cugraph-service-server if I installed it?

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

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

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

Malicious package

cugraph-service-serverPyPI

Malicious code in cugraph-service-server (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-48889

Immediate action

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

pip uninstall cugraph-service-server

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.123.12.0

Indicators of compromise (SHA-256)

20f19db3046be33cd29d8e848580be59afd73bcfb7d26e63f903dec6129dabc3

82e4a6c38746c86b0e3dbed95dcbd6fc069eb716609107d728a323377184ee4f

82f912f9abcdf4498f41f9d9a0b1667f0a81b7fdb1a7f4f850923223474647e6

209732169f89381617bebb66450332691c850533c7812ac92c0ad6b98ebdd1a9

ec895c5fb7a346415a6e5f0d38d6bb50de2e0426d622f438f130431af03e3647

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

Campaign

RLMA-2025-05208GENERIC-standard-pypi-install-pentestRLUA-2026-00242

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks cugraph-service-server-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