Malicious code in riakcs (PyPI)
The riakcs package on PyPI contained malicious code that exfiltrates basic host information (IP address, username) during installation. The package overrides the install command in setup.py to execute the malicious payload when installed.
- Disclosed
- Last updated
- Blast radius
- Any user who installed the malicious riakcs package from PyPI
- Ecosystems
- Attack vectors
- Affected entities
- riakcsPyPI package containing malicious code
The riakcs package published on PyPI contained malicious code designed to exfiltrate basic system information from the host upon installation or module import. The malicious payload was executed by overriding the install command in setup.py, allowing code execution during the package installation process.\n\nThe malicious code collected limited host information such as IP addresses and usernames. According to the OpenSSF malicious packages database, this was classified as a low-harm pentest-style package with limited risk potential.\n\nThe package was identified and reported through the OpenSSF malicious packages project, which maintains a catalog of known malicious packages across package ecosystems.
Indicators of compromise
- Packages
- riakcs
Remediation
- Remove the riakcs package from any systems where it was installed
- Audit systems that installed riakcs for signs of compromise or data exfiltration
- Review network logs for suspicious outbound connections from affected systems
- Use package verification tools and check PyPI advisories before installing packages
- Consider using dependency scanning tools to detect known malicious packages
Sources
- GitHub Advisory GHSA-3849-8v46-m7qx · GitHub Advisory Database
Cite this entry
"Malicious code in riakcs (PyPI)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 8, 2026; last updated August 8, 2026. https://supplychainattack.org/incident/malicious-code-in-riakcs-pypi-1qkmzs
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in reqcrypt-dev (PyPI)
The PyPI package reqcrypt-dev contained malicious code implementing a hidden backdoor. The package masqueraded as an HTTP request library but secretly monitored responses for specific fields and executed their content without user knowledge.
PyPICompromised package - resolvedcritical
Malicious code in deepface-weight (PyPI)
The PyPI package deepface-weight contained malicious code that exfiltrated Telegram session files on import, granting attackers full access to associated Telegram accounts. The package was a typosquat of the legitimate deepface ML library with no actual machine-learning functionality.
PyPICompromised package - resolvedcritical
Malicious code in reqcrypt (PyPI)
The reqcrypt PyPI package contains intentionally hidden malicious code that executes arbitrary Python code from attacker-controlled HTTP responses. The PayloadProcessor unconditionally inspects every HTTP response for specific JSON keys and passes base64/gzip/zlib-decoded values to exec(), enabling remote code execution on any system using the library.
PyPICompromised packageMalicious maintainer - containedcritical
Malicious code in deepface-weights (PyPI)
deepface-weights, a malicious package published to PyPI, contains code that exfiltrates Telegram session credentials on import. The package impersonates the legitimate deepface library but contains only credential-stealing functionality.
PyPICompromised package