Which versions of fire-eye-bcs are malicious?

The following PyPI versions of fire-eye-bcs are flagged malicious: 2, 2.3, 2.4. Treat any of these as compromised.

How do I remediate fire-eye-bcs if I installed it?

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

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

Yes — fire-eye-bcs is associated with the RLMA-2025-06563 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 fire-eye-bcs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fire-eye-bcs (3 malicious versions).

Malicious package

fire-eye-bcsPyPI

Advisory published Dec 23, 2025Updated Dec 24, 2025

fire-eye-bcs is a confirmed malicious PyPI package (MAL-2025-192892) that executes malicious code on install (malicious versions 2, 2.3, 2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fire-eye-bcs (PyPI)

MAL-2025-192892

Immediate action

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

pip uninstall fire-eye-bcs

Malicious versions

3 flagged

22.32.4

Indicators of compromise (SHA-256)

305cde09419a74570cb0e085da193077c99c20d12cf2bc89667b8a7b7f142768

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06563

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fire-eye-bcs-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