Malicious Code Exfiltration in Flaask Package

flaask Updated 27 Dec 2025

Summary

27/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192945: Malicious code in flaask (PyPI). Affects flaask versions 0.0.1 – 0.0.4. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Flaask is a Python package available on PyPI, designed for web development and related functionalities. However, it has been compromised, leading to the inclusion of malicious code that exfiltrates sensitive information from the host system. The package has versions 0.0.1 to 0.0.4, all of which are affected by this vulnerability.

Vulnerability Detail

The vulnerability originates from a malicious actor, identified as kam193, who has embedded code within the Flaask package that exfiltrates basic information about the host system, such as the IP address and username. This code is executed during the installation process due to the package overriding the install command in setup.py. The risk associated with this vulnerability is limited, but it poses a significant threat to user privacy and data security.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall flaask

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users should avoid installing the Flaask package until a patched version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The Flaask package has been compromised to include malicious code that exfiltrates sensitive information from users' systems. It is crucial for users to uninstall the affected versions and refrain from using the package until a secure update is available. Monitoring tools like Vulert can help keep track of vulnerabilities in your software.

See every vulnerability recorded for flaask →

Share this vulnerability

FAQ

Flaask is a Python package intended for web development, but it has been compromised to include malicious code.

The vulnerability allows the package to exfiltrate sensitive information such as your IP address and username during installation.

You should uninstall the Flaask package immediately using the command: pip uninstall flaask.

Currently, there are no patched versions of Flaask available. It is recommended to avoid using this package until a safe version is released.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using Pipfile.lock. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall flaask

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback