Which versions of fireeye-main are malicious?

The following PyPI versions of fireeye-main are flagged malicious: 2.0.0, 2.6. Treat any of these as compromised.

How do I remediate fireeye-main if I installed it?

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

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

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

Search your lockfiles and build artifacts for fireeye-main (2 malicious versions).

Malicious package

fireeye-mainPyPI

Advisory published Dec 23, 2025Updated Dec 24, 2025

fireeye-main is a confirmed malicious PyPI package (MAL-2025-192893) that executes malicious code on install (malicious versions 2.0.0, 2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fireeye-main (PyPI)

MAL-2025-192893

Immediate action

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

pip uninstall fireeye-main

Malicious versions

2 flagged

2.0.02.6

Indicators of compromise (SHA-256)

3e7b8324c03867d3449cffe172138c6ac006f4c26b7872441e19af16877d081f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06564

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fireeye-main-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