Which versions of pysereal are malicious?

The following PyPI versions of pysereal are flagged malicious: 0.0.4, 0.0.6, 0.0.7, 0.0.9, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8. Treat any of these as compromised.

How do I remediate pysereal if I installed it?

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

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

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

Search your lockfiles and build artifacts for pysereal (13 malicious versions).

Malicious package

pyserealPyPI

pysereal is a confirmed malicious PyPI package (MAL-2024-5771) that executes malicious code on install (malicious versions 0.0.4, 0.0.6, 0.0.7…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pysereal (PyPI)

MAL-2024-5771

Immediate action

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

pip uninstall pysereal

Malicious versions

13 flagged

0.0.40.0.60.0.70.0.90.1.00.1.10.1.20.1.30.1.40.1.50.1.60.1.70.1.8

Indicators of compromise (SHA-256)

097ffb440443616bf0649e43ee31ac98ff0b2e7e63b36e57f7051cbe2ed71bc4

c6fc0e3d6625c119dd0e9979b959ec44a78c649821755ebf863382714426cdf9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pysereal (13 malicious versions).
If you installed it — respond
Remove pysereal 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 pysereal 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. pysereal on PyPI has been identified as a malicious package (versions 0.0.4, 0.0.6, 0.0.7, 0.0.9, 0.1.0, 0.1.1, 0.1.2, 0.1.3, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04567RLUA-2024-08997

Credits

ReversingLabs · finder

Detect & block this

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