Which versions of flasq are malicious?

The following PyPI versions of flasq are flagged malicious: 0.1.1, 0.1.2, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate flasq if I installed it?

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

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

Yes — flasq is associated with the 2026-08-flasq, IN-MAL-2026-016911, IN-MAL-2026-016914, IN-MAL-2026-016890, IN-MAL-2026-016910 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 flasq across my projects, lockfiles, and CI pipelines?

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

Malicious package

flasqPyPI

Advisory published Aug 7, 2026Updated Aug 7, 2026

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

Malicious code in flasq (PyPI)

MAL-2026-13487

Immediate action

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

pip uninstall flasq

What this malware does

setup.py registers a custom install cmdclass whose post-install hook is stored as a base64-encoded blob and decoded+exec'd at install time. On Linux, the decoded hook uses urllib.request.urlretrieve to download a binary from https://github.com/totti2188/8gp1Q7iZD3h4VW/releases/download/v1.3A/something, writes it to /tmp/something, chmods it 0755, and spawns it detached via subprocess.Popen(..., start_new_session=True). The download source is an unrelated personal GitHub account; there is no hash or signature verification; and the base64-obfuscation of an install-time code path is an evasion signal. The package advertises itself as 'HTTP client utilities' — this behavior is unrelated to that purpose. The setup.py also defaults the published PyPI name to 'requestss' (name=os.environ.get('PYPI_PACKAGE_NAME', 'requestss')), a one-character typosquat of the popular 'requests' package, indicating the artifact is intended to reach developers mistyping 'requests'.

Package imitates name of a popula library. During installation, obfuscated code downloads a malicious executable and starts it. It then exfiltrates at least cryptocurrency wallet data, probably more.

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

Campaign: 2026-08-flasq

Reasons (based on the campaign):

typosquatting
The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-generic
Downloads and executes a remote executable.
obfuscation
exfiltration-crypto

Malicious versions

4 flagged

0.1.10.1.20.2.00.3.0

Indicators of compromise (SHA-256)

2498f9d207b216ad7438cd262c9136cc5453d288f97a74d4cd44a9a2accf9141

584cd0b30cef0f0b35b72eb0276753fbcb00f15c0ff9ee3cb8555ceba377aa2a

1ef5028c7103dbeab8de4e17eabb8a98a2491cb51ceeaa574029f7aea58dfa98

79bdf17d9c07586ddc0b7121037c2c10019d7be01d2dd49685680a8e876342c6

816f21881e18843f9a15e72f820abb56e7e171c9779ed64bcd6b03ab10f4811b

8ae342e7be11cf89cf0473d0bbf83dbbc8eb6f88e7bf45605f4e89ff54674147

Detection & response playbook

Credential / info stealer

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

Campaign

2026-08-flasqIN-MAL-2026-016911IN-MAL-2026-016914IN-MAL-2026-016890IN-MAL-2026-016910

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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