Which versions of pirlow are malicious?

The following PyPI versions of pirlow are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pirlow if I installed it?

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

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

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

Search your lockfiles and build artifacts for pirlow (version 1.0.0).

Malicious package

pirlowPyPI

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

Malicious code in pirlow (PyPI)

MAL-2024-5549

Immediate action

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

pip uninstall pirlow

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5ac5136944ffd4f469d6b432d700977307ac8393dd1608910f2312b0d7313e54

1730aaf7441ec17eac57df84a881ccbe940e7a141d8451c865ab7b6dbb80556b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04331RLUA-2024-08759

References

Credits

ReversingLabs · finder

Detect & block this

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