Which versions of joule-btp-extension are malicious?

The following PyPI versions of joule-btp-extension are flagged malicious: 0.1.0, 0.1.1, 0.1.3, 0.1.4, 0.1.6. Treat any of these as compromised.

How do I remediate joule-btp-extension if I installed it?

joule-btp-extension 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.

I already installed joule-btp-extension — how do I know if it already compromised me?

If joule-btp-extension 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.

Is joule-btp-extension part of a known attack campaign?

Yes — joule-btp-extension is associated with the 2026-08-joule-btp-extension campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find joule-btp-extension across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for joule-btp-extension (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging joule-btp-extension across your stack and pipelines.

Malicious package

joule-btp-extensionPyPI

joule-btp-extension is a confirmed malicious PyPI package (MAL-2026-13732) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in joule-btp-extension (PyPI)

MAL-2026-13732

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall joule-btp-extension

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.

The OpenSSF Package Analysis project identified 'joule-btp-extension' @ 0.1.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

5 flagged

0.1.00.1.10.1.30.1.40.1.6

Indicators of compromise (SHA-256)

65193272cd9bd3b918d955bb215650b6b89b171e458b3385819f989bc1128049

21a7a58b1f32893cafb7cd9a1b452c5e9138b8fa89c43ebef1b3722205f60596

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for joule-btp-extension (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging joule-btp-extension across your stack and pipelines.
If you installed it — respond
joule-btp-extension 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-btp-extension 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 joule-btp-extension 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

No. joule-btp-extension on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.3, 0.1.4, 0.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-08-joule-btp-extension

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks joule-btp-extension-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database