Which versions of blastchamber-python-pypi are malicious?

The following PyPI versions of blastchamber-python-pypi are flagged malicious: 0.0.4, 0.1.0, 0.2.0, 0.2.2. Treat any of these as compromised.

How do I remediate blastchamber-python-pypi if I installed it?

Remove blastchamber-python-pypi from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed blastchamber-python-pypi — how do I know if it already compromised me?

If blastchamber-python-pypi 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.

Is blastchamber-python-pypi part of a known attack campaign?

Yes — blastchamber-python-pypi is associated with the RLMA-2025-06555 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 blastchamber-python-pypi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for blastchamber-python-pypi (4 malicious versions).

Malicious package

blastchamber-python-pypiPyPI

Advisory published Dec 23, 2025Updated Dec 24, 2025

blastchamber-python-pypi is a confirmed malicious PyPI package (MAL-2025-192891) that executes malicious code on install (malicious versions 0.0.4, 0.1.0, 0.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in blastchamber-python-pypi (PyPI)

MAL-2025-192891

Immediate action

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

pip uninstall blastchamber-python-pypi

Malicious versions

4 flagged

0.0.40.1.00.2.00.2.2

Indicators of compromise (SHA-256)

2c7eb8338cd27ff8b5034d39ee52ef1540c025589e08299a7346234598d46604

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for blastchamber-python-pypi (4 malicious versions).
If you installed it — respond
Remove blastchamber-python-pypi from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If blastchamber-python-pypi 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

No. blastchamber-python-pypi on PyPI has been identified as a malicious package (versions 0.0.4, 0.1.0, 0.2.0, 0.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06555

Credits

ReversingLabs · finder

Detect & block this

O3 blocks blastchamber-python-pypi-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database