Which versions of flatfox-api-python are malicious?

The following PyPI versions of flatfox-api-python are flagged malicious: 0.1, 0.2, 0.3. Treat any of these as compromised.

How do I remediate flatfox-api-python if I installed it?

flatfox-api-python 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 flatfox-api-python — how do I know if it already compromised me?

If flatfox-api-python was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is flatfox-api-python part of a known attack campaign?

Yes — flatfox-api-python 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 flatfox-api-python across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flatfox-api-python (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flatfox-api-python across your stack and pipelines.

Malicious package

flatfox-api-pythonPyPI

Malicious code in flatfox-api-python (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6973

Immediate action

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

pip uninstall flatfox-api-python

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.

The OpenSSF Package Analysis project identified 'flatfox-api-python' @ 0.3 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

d82a5bf63c0c510997a6d8d438e71f8522351b6e4c0cbca760d856ef2b623342

688dcb86e71feda7dff5b609da6dcd8dae0e113c2bc709b76592ab122c10be88

a81db9eb6d8c8eb51eecf49610e1282097b77630ccb58b6eef3e2f002e5fe0e2

e70b0b90ab8583f9dd6104ada5da8f42c68b76d4ab9244a4b0904faeba37a8ef

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flatfox-api-python (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flatfox-api-python across your stack and pipelines.
If you installed it — respond
flatfox-api-python 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 flatfox-api-python was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks flatfox-api-python before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. flatfox-api-python on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3 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)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks flatfox-api-python-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