Which versions of pyptllm are malicious?

The following PyPI versions of pyptllm are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate pyptllm if I installed it?

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

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

Yes — pyptllm 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 pyptllm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pyptllm (version 0.2).

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

Malicious package

pyptllmPyPI

Advisory published Jun 15, 2026Updated Jun 17, 2026

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

Malicious code in pyptllm (PyPI)

MAL-2026-5821

Immediate action

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

pip uninstall pyptllm

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

0.2

Indicators of compromise (SHA-256)

e06c1d9a31b3d159c7db950a10dc5678dceac45317a87542e0d382a4f688f951

3a585ad79e47fd7926602b6e6c52221e590b3faf13609cba8107970c61af5557

3f7b278e357a7d8b2e9478016a91a0baeb78e6608ec718ed3a2dacfe1fc4ba3e

fa41ae2f65e7cb8e2acbf3c242271656f489b615a11473d00b48dd83e69633f4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pyptllm (version 0.2).
If you installed it — respond
pyptllm 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 pyptllm 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. pyptllm on PyPI has been identified as a malicious package (version 0.2 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 pyptllm-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