richxPyPI
Advisory published Updated
richx is a confirmed malicious PyPI package (MAL-2025-191658) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 1.0.0, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in richx (PyPI)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for richx (4 malicious versions).
If you installed it — respond
richx 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 richx 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
Campaign
References
Credits
- Kamil Mańkowski (kam193)
- ReversingLabs · finder
Detect & block this
O3 blocks richx-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.