Which versions of coolbox are malicious?

The following PyPI versions of coolbox are flagged malicious: 0.4.1, 0.4.2. Treat any of these as compromised.

How do I remediate coolbox if I installed it?

coolbox 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 coolbox — how do I know if it already compromised me?

If coolbox 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 coolbox part of a known attack campaign?

Yes — coolbox is associated with the 2026-06-compr-woodpecker, IN-MAL-2026-005804 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 coolbox 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 coolbox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coolbox across your stack and pipelines.

Malicious package

coolboxPyPI

Malicious code in coolbox (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5295

Immediate action

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

pip uninstall coolbox

What this malware does

The wheel installs coolbox-setup.pth, a Python path-configuration file that Python auto-loads at every interpreter startup (any python invocation system-wide, not just import coolbox). The.pth uses exec() on an obfuscated string that downloads the Bun JavaScript runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/bun-{platform}-{arch}.zip to /tmp/b/bun, chmods it executable, and runs a glob-located _index.js sibling under it. A .bun_ran sentinel file gates one-shot execution. CoolBox is advertised as a Python genomics/Jupyter visualization library (GangCaoLab, BMC Bioinformatics 2021) and has no legitimate need to install or execute a JavaScript runtime. The release also shows hijack fingerprints: coolbox/__init__.py declares __version__ = '0.4.0' while the dist-info METADATA declares Version: 0.4.1, and RECORD additively references the prior coolbox-0.4.0.dist-info/ alongside the new coolbox-setup.pth — consistent with a malicious republish layered on top of the legitimate prior release. The _index.js payload is not listed in RECORD, indicating it is staged from another source. Installer harm: any system that installs this wheel will execute attacker-controlled JavaScript under the Bun runtime on every subsequent python startup, with the user's privileges.

Versions 0.4.1, 0.4.2 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

2 flagged

0.4.10.4.2

Indicators of compromise (SHA-256)

5c2dc2f03691017c67f2ef9805c4974416d935298b4748b033bfb7f487ede251

f0d5fde6bb63a9bdd47ede4cdf19e54d636016848ad9e780a0db4d96138c2d6f

6120318ad0beb72f5fe01fbceb6a2bb29b2c93c277b4a5fe2b5d7f148bcd30d8

da9448cdfb3593bc9434cbc09686ea2d8bc73f5b531e45d13229949e14aadbf8

c55bfdad112134e980af7568a9138be1e4b940f7bfbeebad2b0f85d9337a0f44

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 coolbox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coolbox across your stack and pipelines.
If you installed it — respond
coolbox 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 coolbox 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 coolbox 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. coolbox on PyPI has been identified as a malicious package (versions 0.4.1, 0.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-compr-woodpeckerIN-MAL-2026-005804

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks coolbox-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