Which versions of guypy are malicious?

The following PyPI versions of guypy are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate guypy if I installed it?

Remove guypy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed guypy — how do I know if it already compromised me?

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

Yes — guypy is associated with the RLMA-2024-03972, RLUA-2024-08331 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 guypy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for guypy (version 0.1.0).

Malicious package

guypyPyPI

guypy is a confirmed malicious PyPI package (MAL-2024-5190) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in guypy (PyPI)

MAL-2024-5190

Immediate action

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

pip uninstall guypy

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

498a7169f5c708d381692adb157971c9ed23c832f8711a7709b29ae665c5bb30

027a0954575fb3a9c17bed94ea68e750f0edd4e34433366091b93a702070996e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for guypy (version 0.1.0).
If you installed it — respond
Remove guypy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If guypy 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. guypy on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03972RLUA-2024-08331

Credits

ReversingLabs · finder

Detect & block this

O3 blocks guypy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database