joule-sbx-pocPyPI
Advisory published Updated
joule-sbx-poc is a confirmed malicious PyPI package (MAL-2026-13756) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in joule-sbx-poc (PyPI)
What this malware does
During installation, the code exfiltrates basic information and exfiltrates more information to a localhost service as well as starts a reverse shell there. It seems to be an internal test that was uploaded to a public repository.
Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.
Campaign: 2026-08-joule-btp-extension
Reasons (based on the campaign):
-
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
-
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for joule-sbx-poc (version 0.1.0).
If you installed it — respond
joule-sbx-poc 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 joule-sbx-poc 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) · reporter
Detect & block this
O3 blocks joule-sbx-poc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.