Which versions of llmfree are malicious?

The following PyPI versions of llmfree are flagged malicious: 2.21. Treat any of these as compromised.

How do I remediate llmfree if I installed it?

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

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

Yes — llmfree is associated with the 2026-06-easyaillm 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 llmfree across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for llmfree (version 2.21).

Part of a larger attack: 2026-06-easyaillm published 18 malicious packages. See the full campaign →

Malicious package

llmfreePyPI

Advisory published Jun 15, 2026Updated Jun 17, 2026

llmfree is a confirmed malicious PyPI package (MAL-2026-5796) that steals credentials and exfiltrates sensitive data (malicious version 2.21). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in llmfree (PyPI)

MAL-2026-5796

Immediate action

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

pip uninstall llmfree

What this malware does

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

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

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

1 flagged

2.21

Indicators of compromise (SHA-256)

ef9f18729f90b5872084b7c7e822ee7fedd40a1074e25d461350b2740433f11d

b9b6109407ca90a4bb4119a65337962da99eb725177ceb56f2a439c053117f40

17ddbaa4410f97c50c79a60ccee79ca92c9d55ae13cfd79fe9b3f1d40e1a8c60

e779d2361b98c48a801fb29dedf2931f94b4264314d074895e14482ad0d5a15f

Detection & response playbook

Credential / info stealer

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

Campaign

2026-06-easyaillm

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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