Which versions of piirgg are malicious?

The following PyPI versions of piirgg are flagged malicious: 0.2, 0.3, 0.4, 0.6. Treat any of these as compromised.

How do I remediate piirgg if I installed it?

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

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

Yes — piirgg is associated with the RLMA-2026-02104 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 piirgg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for piirgg (4 malicious versions).

Malicious package

piirggPyPI

Advisory published Jul 7, 2026Updated Jul 9, 2026

piirgg is a confirmed malicious PyPI package (MAL-2026-7457) that executes malicious code on install (malicious versions 0.2, 0.3, 0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in piirgg (PyPI)

MAL-2026-7457

Immediate action

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

pip uninstall piirgg

Malicious versions

4 flagged

0.20.30.40.6

Indicators of compromise (SHA-256)

5ac8bf0f897e409c2e63ad0421c9de99d276e924c783cee87b33e53c37c14020

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02104

Credits

ReversingLabs · finder

Detect & block this

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