Which versions of flaask are malicious?

The following PyPI versions of flaask are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate flaask if I installed it?

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

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

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

Search your lockfiles and build artifacts for flaask (4 malicious versions).

Malicious package

flaaskPyPI

Advisory published Dec 27, 2025Updated Dec 31, 2025

flaask is a confirmed malicious PyPI package (MAL-2025-192945) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flaask (PyPI)

MAL-2025-192945

Immediate action

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

pip uninstall flaask

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

4 flagged

0.0.10.0.20.0.30.0.4

Indicators of compromise (SHA-256)

f528a95e44d680b45bbab0cb120d39e27bf1c5bdd4e61d4a5e410c9efeb59539

dcf730d86bfb8fcf6061cc07bb01e5a845f20b8f204bb276753b2a87b46e6afb

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for flaask (4 malicious versions).
If you installed it — respond
flaask 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 flaask 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. flaask on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4 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 flaask-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