Which versions of bitranox-coloredlogs are malicious?

The following PyPI versions of bitranox-coloredlogs are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate bitranox-coloredlogs if I installed it?

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

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

Yes — bitranox-coloredlogs is associated with the RLMA-2025-03548 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 bitranox-coloredlogs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bitranox-coloredlogs (version 0.0.1).

Malicious package

bitranox-coloredlogsPyPI

bitranox-coloredlogs is a confirmed malicious PyPI package (MAL-2025-6463) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bitranox-coloredlogs (PyPI)

MAL-2025-6463

Immediate action

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

pip uninstall bitranox-coloredlogs

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

23c589f116d0bb94b7d4ba26ccbef811b1fe84c3d1e2545ce5c79ce6ef7e4952

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bitranox-coloredlogs (version 0.0.1).
If you installed it — respond
Remove bitranox-coloredlogs 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 bitranox-coloredlogs 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. bitranox-coloredlogs on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03548

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bitranox-coloredlogs-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