Which versions of pyrologin are malicious?

The following PyPI versions of pyrologin are flagged malicious: 2.2, 2.6, 2.7. Treat any of these as compromised.

How do I remediate pyrologin if I installed it?

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

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

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

Search your lockfiles and build artifacts for pyrologin (3 malicious versions).

Malicious package

pyrologinPyPI

pyrologin is a confirmed malicious PyPI package (MAL-2024-5769) that executes malicious code on install (malicious versions 2.2, 2.6, 2.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pyrologin (PyPI)

MAL-2024-5769

Immediate action

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

pip uninstall pyrologin

Malicious versions

3 flagged

2.22.62.7

Indicators of compromise (SHA-256)

b65592a2ded3ff789006303b0d0d56270588f79d1a03af2be25927c2a0fe95aa

c358bfa0dcb3010571650e2f8d3c12618381b1407aa0b86baa1eea6ef0d59255

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04565RLUA-2024-08995

References

Credits

ReversingLabs · finder

Detect & block this

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