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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for llmfree (version 2.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llmfree across your stack and pipelines.

Malicious package

llmfreePyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for llmfree (version 2.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llmfree across your stack and pipelines.
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 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 llmfree 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. 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