Which versions of graphcore-cloud-tools are malicious?

The following PyPI versions of graphcore-cloud-tools are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate graphcore-cloud-tools if I installed it?

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

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

Yes — graphcore-cloud-tools is associated with the RLMA-2024-08329, GENERIC-standard-pypi-install-pentest, RLUA-2026-00363 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 graphcore-cloud-tools 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 graphcore-cloud-tools (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging graphcore-cloud-tools across your stack and pipelines.

Malicious package

graphcore-cloud-toolsPyPI

Malicious code in graphcore-cloud-tools (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10032

Immediate action

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

pip uninstall graphcore-cloud-tools

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1434ebef39d278f607976de853350739f7d165f714ee774230c6e3f2fa312074

fddcb778cb9529c47d1ccdd328bf40f4d46c18080845ded222bb8ef80e7c3fbd

ac46cb60f0875363e708276c64f0c8fa73c50f57eed28170f94437a5954f89fd

64b515588191e1395afe3894941ad767fb133f706bf419f9698891f2881bd8b8

258a27af13b263148227e75cdd6550d7395ef41591683aa92387f24b425ce002

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

Campaign

RLMA-2024-08329GENERIC-standard-pypi-install-pentestRLUA-2026-00363

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks graphcore-cloud-tools-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