Which versions of gpu-free-ai are malicious?

The following PyPI versions of gpu-free-ai are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate gpu-free-ai if I installed it?

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

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

Yes — gpu-free-ai is associated with the 2025-07-gpu-free-ai 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 gpu-free-ai across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gpu-free-ai (2 malicious versions).

Malicious package

gpu-free-aiPyPI

Advisory published Jul 10, 2025Updated Dec 12, 2025

gpu-free-ai is a confirmed malicious PyPI package (MAL-2025-191743) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gpu-free-ai (PyPI)

MAL-2025-191743

Immediate action

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

pip uninstall gpu-free-ai

What this malware does

Code attempts to exfiltrate any env variable containing "key" in name. This action is triggered on multiple occasions thanks to overwriting module loading and patching.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-07-gpu-free-ai

Reasons (based on the campaign):

exfiltration-env-variables

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

e06bedb403f82354b741ed70cae2d7483b88d3dd8751993f885edd31f8e4f3ef

0846b9b18e7af4ddef44ca9cb92d5543ace58ee3f171080b1570c3f044749dec

3812b164cfb6c37993bf4f7398b4f6f33be6c6f15ace0183046bfedcae029e5b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gpu-free-ai (2 malicious versions).
If you installed it — respond
gpu-free-ai 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 gpu-free-ai 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. gpu-free-ai on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-gpu-free-ai

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks gpu-free-ai-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