Which versions of pycryptoshuffle are malicious?

The following PyPI versions of pycryptoshuffle are flagged malicious: 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate pycryptoshuffle if I installed it?

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

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

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

Search your lockfiles and build artifacts for pycryptoshuffle (6 malicious versions).

Malicious package

pycryptoshufflePyPI

Advisory published Jul 7, 2026Updated Jul 23, 2026

pycryptoshuffle is a confirmed malicious PyPI package (MAL-2026-7458) that executes malicious code on install (malicious versions 1.0.6, 1.0.7, 1.0.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pycryptoshuffle (PyPI)

MAL-2026-7458

Immediate action

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

pip uninstall pycryptoshuffle

Malicious versions

6 flagged

1.0.61.0.71.0.81.0.91.1.01.1.1

Indicators of compromise (SHA-256)

8ea28e512fa7ff00685fcf7df75f8a311244d8ccaab19c3464f73bfdd0eafd3d

a80632b3dcbf1f90374bca61ecbe41f30dd52faf3eb8bddb649e0339e81b2097

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pycryptoshuffle (6 malicious versions).
If you installed it — respond
Remove pycryptoshuffle 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 pycryptoshuffle 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. pycryptoshuffle on PyPI has been identified as a malicious package (versions 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02107RLUA-2026-05391

Credits

ReversingLabs · finder

Detect & block this

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