Which versions of flasl are malicious?

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

How do I remediate flasl if I installed it?

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

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

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

Malicious package

flaslPyPI

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

MAL-2025-926

Immediate action

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

pip uninstall flasl

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

2 flagged

3.1.8.dev03.1.9.dev0

Indicators of compromise (SHA-256)

c19cc2ad84b3b08924927bcc8c2514694cd955c3f351f0836b329828fcca5898

8adf4fbbde66650c1a4b0db9f9a3eb8b389269d4cc4370457da70ef4405185e5

15f6805748d19912e476158c87c5c50c0f8b50bdfa82d8c6e24d996e7c38880c

ca8e671c7f3767f023e9a33a039730da49fde3d020dcdea53f9ceed8cbc7da47

5bd9c7632f737f5ff3ba5c5c26fdbe4bba4a3d9e5ce17b6259748879e50b53a8

7b389167a2b78e9489c05c61ef32cbdd9e9f775433f0daea92b64c81a5668305

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

Campaign

RLMA-2025-004652024-12-reqesstRLUA-2026-00329

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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