Which versions of ibreak are malicious?

The following PyPI versions of ibreak are flagged malicious: 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate ibreak if I installed it?

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

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

Yes — ibreak is associated with the RLMA-2026-05388 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 ibreak across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ibreak (3 malicious versions).

Malicious package

ibreakPyPI

Advisory published Jul 20, 2026Updated Jul 23, 2026

ibreak is a confirmed malicious PyPI package (MAL-2026-10909) that executes malicious code on install (malicious versions 0.1.2, 0.1.3, 0.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ibreak (PyPI)

MAL-2026-10909

Immediate action

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

pip uninstall ibreak

Malicious versions

3 flagged

0.1.20.1.30.1.4

Indicators of compromise (SHA-256)

fa89f7e02266a41e40bfa56da23c825cb527c1edf333b3e5320d24b70afb3f51

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05388

Credits

ReversingLabs · finder

Detect & block this

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