Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

pyptllmPyPI

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

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
  1. Find it

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

  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.

  3. Did it already run?

    If pyptllm 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.

  4. How O3 protects you

    O3 blocks pyptllm 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. 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.