Which versions of pystlete are malicious?

The following PyPI versions of pystlete are flagged malicious: 2.9. Treat any of these as compromised.

How do I remediate pystlete if I installed it?

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

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

Yes — pystlete is associated with the RLMA-2024-09011, 2024-07-kiwi-infostealer, RLUA-2026-00648 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 pystlete 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 pystlete (version 2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pystlete across your stack and pipelines.

Malicious package

pystletePyPI

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

MAL-2024-10125

Immediate action

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

pip uninstall pystlete

What this malware does

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

Campaign: 2024-07-kiwi-infostealer

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

2.9

Indicators of compromise (SHA-256)

98ae5eac380538c5efb0b7729c0ce4920f5a78f7103efb08171292e2b247ad24

b5615c0ec052668e203630f9b545437ef427612f9aa437c39099cd5a87ff7ba5

e5d093c6ce26c2d62ba07cc7fc8e0a5441f9e58bfc62943f6032dad8abefde57

eb30c86b3479508da3c05c1c2d2dc529e0db8952e7b60989850263acd5c0e8b3

d6ad725bcd700145fea17b0ef116213f3dc533fc2e90213a40c774c80c5df554

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 pystlete (version 2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pystlete across your stack and pipelines.
If you installed it — respond
pystlete 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 pystlete 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 pystlete 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. pystlete on PyPI has been identified as a malicious package (version 2.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-090112024-07-kiwi-infostealerRLUA-2026-00648

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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