Which versions of pygments-richstyle are malicious?

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

How do I remediate pygments-richstyle if I installed it?

pygments-richstyle is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed pygments-richstyle — how do I know if it already compromised me?

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

Yes — pygments-richstyle is associated with the RLMA-2025-05628, 2025-10-asynhttp, RLUA-2026-00634 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 pygments-richstyle across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pygments-richstyle (version 1.0.0).

Part of a larger attack: 2025-10-asynhttp published 8 malicious packages. See the full campaign →

Malicious package

pygments-richstylePyPI

Advisory published Oct 31, 2025Updated Mar 19, 2026

pygments-richstyle is a confirmed malicious PyPI package (MAL-2025-191654) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pygments-richstyle (PyPI)

MAL-2025-191654

Immediate action

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

pip uninstall pygments-richstyle

What this malware does

Packages silently decrypt content hidden in a dependency and load them as Python extension modules.

In the first wave, those are copies of legitimate aiohttp and aiohappyeyeballs packages. In the second wave, malicious packages created good-looking forks of legitimate rich and pigments packages.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-10-asynhttp

Reasons (based on the campaign):

typosquatting
exfiltration-generic
obfuscation
clones-real-package
native-extension

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6b49aa9502d6164b44069711b872ae64859f1ee6c43f5cd65745a3fd13cc5d6f

1a522c8b8020b2bc892dccb2ac852a0a95c0eeb3fc0f94f7e4fff0da98979fa1

ed44cafe4fd7aebba15cdc8a14058888e3071523ae21ea13f827a1b9713033cd

a965f61b1e51e6c96a8987633eaf2f23001320e4c6b884c33603230c66798e74

93c92401274f72ed49706fcca3207624059529f6f2e375ce2033a831a85d17e3

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pygments-richstyle (version 1.0.0).
If you installed it — respond
pygments-richstyle is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pygments-richstyle 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. pygments-richstyle 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-2025-056282025-10-asynhttpRLUA-2026-00634

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pygments-richstyle-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database