Which versions of fflask are malicious?

The following PyPI versions of fflask are flagged malicious: 3.1.8.dev0, 3.1.9.dev0, 3.2.0.dev0. Treat any of these as compromised.

How do I remediate fflask if I installed it?

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

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

Yes — fflask is associated with the RLMA-2025-00462, 2024-12-reqesst, RLUA-2026-00322 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 fflask 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 fflask (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fflask across your stack and pipelines.

Malicious package

fflaskPyPI

Malicious code in fflask (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-923

Immediate action

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

pip uninstall fflask

What this malware does

Importing the module downloads and starts an infostealer attempting to exfiltrate data and establishing persistence through autorun directory.

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

Campaign: 2024-12-reqesst

Reasons (based on the campaign):

infostealer
peristence-autorun
typosquatting
exfiltration-generic
Downloads and executes a remote executable.
clones-real-package
dependency-confusion
exfiltration-browser-data
exfiltration-crypto

Malicious versions

3 flagged

3.1.8.dev03.1.9.dev03.2.0.dev0

Indicators of compromise (SHA-256)

aadf19ab3a430e1d1949079802ffbf8b13de48de3ee9be4a8fc27b01cb1b7ee3

aa375ec26bb7f689088c60ca1503882a9f33f5ba939c445a716bb1f2c2b1cf56

106052056ac243ab1b11c7bbf3a04ff9f1b408cf92616fa635242b4230490d2f

8af60ad3fafe1f050bde40b73f51922a241da7f944c90215168038782d8d9554

868b80209443d3671c756469d08c6d4a75cc089eb5fdc31b62ff18d526fcf9d4

da0142bf62d2974ee855268c35f488d3cffa02e7ae27de8ef54d7374f3ad1bf6

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 fflask (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fflask across your stack and pipelines.
If you installed it — respond
fflask 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 fflask 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 fflask 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. fflask on PyPI has been identified as a malicious package (versions 3.1.8.dev0, 3.1.9.dev0, 3.2.0.dev0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-004622024-12-reqesstRLUA-2026-00322

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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