pojang-resorterPyPI
Advisory published Updated
pojang-resorter is a confirmed malicious PyPI package (MAL-2024-11660) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.2, 0.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pojang-resorter (PyPI)
What this malware does
Early versions used overriding install command to take screenshots, then it moved to automated installing an infostealer. Later the behaviour was changed and looks like being a toolkit to install malware, yet, depending on version, containing an automated infostealer installation. The exact code is partially hidden behind different obfuscation methods.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2024-08-pojang-resorter
Reasons (based on the campaign):
-
infostealer
-
The package overrides the install command in setup.py to execute malicious code during installation.
-
Downloads and executes a remote executable.
-
obfuscation
-
exfiltration-generic
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for pojang-resorter (56 malicious versions).
If you installed it — respond
pojang-resorter 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 pojang-resorter 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 pojang-resorter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.