Which versions of pyloy are malicious?

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

How do I remediate pyloy if I installed it?

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

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

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

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

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

Malicious package

pyloyPyPI

Advisory published Sep 4, 2024Updated Mar 19, 2026

pyloy is a confirmed malicious PyPI package (MAL-2024-10119) 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 pyloy (PyPI)

MAL-2024-10119

Immediate action

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

pip uninstall pyloy

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)

6b9abfa8480d9cb408b52d59dfd038dc6d1b6e6896ce9cae74da74f18ae82031

2eee91f420f40c791e2da4b56eeef80833d691c773eb0813462cc5020b91218f

44deac488d2a8cdb533662db66592095a36ab35a491b4e9415c597cde0d37eab

fcdc9a095bbbefcbbf13c28a209f522deabee6a34ce16b5406f24746792f76e2

753ef9f20bfb2780e35dbddb25ae4d19922c232611f4bdb62530a1874f244c18

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pyloy (version 0.0.1).
If you installed it — respond
pyloy 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 pyloy 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. pyloy 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-089672024-08-embeds-RealtekHDAudioManagerRLUA-2026-00640

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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