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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flag-leak-r (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flag-leak-r across your stack and pipelines.

Malicious package

flag-leak-rPyPI

Malicious code in flag-leak-r (PyPI) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flag-leak-r (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flag-leak-r across your stack and pipelines.
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 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 flag-leak-r 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. 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