What does the flag-leak-r malware do?

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: GENERIC-questionable-pentest Reasons (based on the campaign): - exfiltration-env-variables - exfiltration-generic - The package overrides the install command in setup.py to execute malicious code during installation. - typosquatting The OpenSSF Package Analysis project identified 'flag-leak-r' @ 0.1.0 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activ

Which versions of flag-leak-r are malicious?

The following PyPI versions of flag-leak-r are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate flag-leak-r if I installed it?

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

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

Yes — flag-leak-r is associated with the GENERIC-questionable-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 flag-leak-r across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for flag-leak-r (version 0.1.0).

Malicious package

flag-leak-rPyPI

Advisory published Sep 6, 2024Updated Dec 12, 2025

flag-leak-r is a confirmed malicious PyPI package (MAL-2024-9446) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flag-leak-r (PyPI)

MAL-2024-9446

Immediate action

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

pip uninstall flag-leak-r

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

The OpenSSF Package Analysis project identified 'flag-leak-r' @ 0.1.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

095f9908b28b3dfb45e9f5e8d291ad2492bb271f23e5f4b714328ba722252838

747eacc8dcf63ec5f77aaebbb960d3a811e31270c721aa54b7a2c037d79104c3

88c1df06a02daf1a911f895df0bd495b0f0d2e72f3b9ad45fe5a837575379c9e

0c10b287871d2837d148658da49d9237d930ed53f40e982a5592b664f184e345

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for flag-leak-r (version 0.1.0).
If you installed it — respond
flag-leak-r 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 flag-leak-r 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. flag-leak-r on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-questionable-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks flag-leak-r-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