Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
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

On pip install, setup.py runs a collect_and_exfiltrate() routine that reads /private/etc/passwd, /private/etc/hosts, and /private/etc/sudoers; captures selected environment variables (HOME, USER, LOGNAME, VIRTUAL_ENV, PATH, PIP_CACHE_DIR, npm_config_prefix, GIT_EDITOR); recursively globs the installer's $HOME and current working directory and reads up to 4096 bytes of each file; and additionally invokes os.system("cat /private/etc/passwd"). The collected data is JSON-serialized and POSTed via urllib to a hardcoded ATTACKER_URL (currently the placeholder http://127.0.0.1:4445/collect, with an author comment 'replace before deploying') using a spoofed 'User-Agent: pip/23.0' header to blend with pip traffic, and all exceptions are silently swallowed. setup.py also writes a marker file '.joule-btp-extension-was-here' into $VIRTUAL_ENV/bin, demonstrating write access to the installer's virtualenv bin directory for persistence. The package's own docstring declares it a proof-of-concept sandbox-escape supply-chain attack targeting SAP Joule Desktop on macOS; the PoC framing does not change what the code does on install: it harvests installer files and identity data and beacons them off-host.

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
c4114daaef1171677fa1042ab30ea5104722c46e0fd9b7c71260b2dbeae61b8e
101702a7339ec70d8cec7d46df8650dbd393734e9b884e0c19118117a0491b1c
ed958edb4a9ec676c868ec6dee06a854bacfa7601cefa8ccaab72bca1badcf5f
63afca9a25a2f6e1d75ae3153d2f1b4e7a0d70649ce402e1cbe1e645478d99ba
91439e7a69d936aa8a65b16561f48e9d9abab26fc8e3af4087da8d367cfd2210
5bbf11309d88c0af577c0d50026c8829e8d43503ba900dd9eef1c76eea012697

Detection & response playbook

Credential / info stealer
  1. 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.

  2. 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.

  3. 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.

  4. 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-extensionIN-MAL-2026-017357IN-MAL-2026-017358IN-MAL-2026-017373IN-MAL-2026-017371IN-MAL-2026-017372

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter
  • 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.

Explore

joule-btp-extension (PyPI) malicious package — MAL-2026-13732 | O3 Security