pygame-renderkitPyPI
pygame-renderkit is a confirmed malicious PyPI package (MAL-2026-14587) that steals credentials and exfiltrates sensitive data (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pygame-renderkit (PyPI)
What this malware does
setup.py registers a custom install command that forks a daemonized child during pip install and executes a base64-encoded Python payload via exec(compile(...)). The decoded payload connects to a hardcoded C2 host at 5uj0a8ziyu.localto.net:3900 and provides an interactive reverse shell by duplicating the socket onto stdin/stdout/stderr of /bin/bash (via pty.spawn) or /bin/sh -i, with a 15-second reconnect loop. It also enumerates environment variables matching API, TOKEN, KEY, SECRET, PASS, CRED, AUTH, AWS, AZURE, GCP, OPENAI, ANTHROPIC, and MANUS, reads /etc/passwd, /etc/sudoers, /etc/shadow, ~/.bash_history, and /opt/.manus/current/config, and sends the collected data over TCP to the same host framed with [EXFIL]/[ENDEXFIL] markers. Persistence is established by writing /tmp/.rk_recon.py, installing a per-minute crontab entry, dropping a renderkit.service systemd user unit with Restart=always, and writing /etc/sudoers.d/.renderkit granting the current user NOPASSWD: ALL. The payload is stored as a base64-encoded template with %%HOST%%/%%PORT%% placeholders and the installer forks with start_new_session=True to hide from pip output. The package presents as a pygame utility; none of this behavior matches that stated purpose.
During installation, the package attempts to exfiltrate sensitive environment variables and files, establish persistence and open reverse shell.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-pygame-renderkit
Reasons (based on the campaign):
-
persistence
-
The package overrides the install command in setup.py to execute malicious code during installation.
-
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
-
files-exfiltration
-
exfiltration-env-variables
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pygame-renderkit (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pygame-renderkit across your stack and pipelines.
If you installed it — respond
pygame-renderkit 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 pygame-renderkit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pygame-renderkit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks pygame-renderkit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.