Which versions of 0xfighter3 are malicious?

The following PyPI versions of 0xfighter3 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate 0xfighter3 if I installed it?

0xfighter3 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed 0xfighter3 — how do I know if it already compromised me?

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

Yes — 0xfighter3 is associated with the GENERIC-standard-pypi-install-pentest 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 0xfighter3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 0xfighter3 (version 0.1).

Malicious package

0xfighter3PyPI

Advisory published Aug 26, 2026Updated Aug 26, 2026

0xfighter3 is a confirmed malicious PyPI package (MAL-2026-14525) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 0xfighter3 (PyPI)

MAL-2026-14525

Immediate action

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

pip uninstall 0xfighter3

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

5a97978609c71d681a69a2da613c5e52b257a2062d7805b8db25243db50ff36f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for 0xfighter3 (version 0.1).
If you installed it — respond
0xfighter3 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If 0xfighter3 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. 0xfighter3 on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks 0xfighter3-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database