Which versions of flowfix are malicious?

The following PyPI versions of flowfix are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate flowfix if I installed it?

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

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

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

Search your lockfiles and build artifacts for flowfix (2 malicious versions).

Malicious package

flowfixPyPI

Advisory published Mar 6, 2026Updated Mar 15, 2026

flowfix is a confirmed malicious PyPI package (MAL-2026-1276) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flowfix (PyPI)

MAL-2026-1276

Immediate action

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

pip uninstall flowfix

What this malware does

The package hides code to download and open remote content. The current code seems to be a bit broken as the final URL is not correct, but the code holds also reference to a URL serving an infostealer executable.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-flowfix

Reasons (based on the campaign):

obfuscation
infostealer
Downloads and executes a remote executable.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

77c3304c8fcc8e0cdf2ac450babf481ff0ee3e93cb3c4213c6b4fa8d80cf4137

a3acc10f58ade4578805fe35e94db0692ca90b7133ce5b4f6f04787305208afe

Detection & response playbook

Credential / info stealer

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

Campaign

2026-03-flowfix

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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