Which versions of pysleek are malicious?

The following PyPI versions of pysleek are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pysleek if I installed it?

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

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

Yes — pysleek is associated with the RLMA-2024-11133, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00646 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 pysleek across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pysleek (version 0.0.1).

Part of a larger attack: 2024-08-embeds-RealtekHDAudioManager published 40 malicious packages. See the full campaign →

Malicious package

pysleekPyPI

Advisory published Sep 4, 2024Updated Mar 19, 2026

pysleek is a confirmed malicious PyPI package (MAL-2024-11676) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pysleek (PyPI)

MAL-2024-11676

Immediate action

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

pip uninstall pysleek

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5789274278925b29e2e2c3030eeea2aec7717694a881ed8fe9752d37cacb83f9

adba0a2b1eace6892e9ff70dfce1189619e0f336bd7af9f87ed59fcf72308215

ebcd258899197196fca41e03c7a6781f5087b42fd37c0276ae9a892bef8d4910

e13b3e70b42b227dd683474a5fa920d41107871c81196f34e7a632edf09afa0b

0b422c55acb7b5d2d908ae77e0046001f2e05a56222bbc29d2298a344b3bf904

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2024-111332024-08-embeds-RealtekHDAudioManagerRLUA-2026-00646

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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