Which versions of falador are malicious?

The following PyPI versions of falador are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate falador if I installed it?

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

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

Yes — falador is associated with the GENERIC-hackerone-bugbounty 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 falador across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for falador (version 99.0.1).

Malicious package

faladorPyPI

Advisory published Mar 11, 2026Updated Apr 10, 2026

falador is a confirmed malicious PyPI package (MAL-2026-1350) that steals credentials and exfiltrates sensitive data (malicious version 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in falador (PyPI)

MAL-2026-1350

Immediate action

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

pip uninstall falador

What this malware does

During installation or import, the package exfiltrates basic information in a dependency confusion attempt. The user identifies themselves as a HackerOne user abusing the PyPI for the purpose of a bug bounty program.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-hackerone-bugbounty

Reasons (based on the campaign):

dependency-confusion
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

1d66c45b27d4ff7595d8a13a91515450c248dc50a6531199f0254bbd9d6440bb

8c95d5e7064d94eb2ee6c1b3940eec900080b63ea754a2293177a729497515f4

35874bb61ba6298fdd334d7989928f5072d70846eaeeebb9b5c24538c996ad26

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-hackerone-bugbounty

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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