Which versions of faest are malicious?

The following PyPI versions of faest are flagged malicious: 0.14.6. Treat any of these as compromised.

How do I remediate faest if I installed it?

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

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

Yes — faest is associated with the 2024-09-old-faest 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 faest 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 faest (version 0.14.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging faest across your stack and pipelines.

Malicious package

faestPyPI

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

MAL-2024-12269

Immediate action

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

pip uninstall faest

What this malware does

When using this library to do any request, a "validate_origin" function is called (L1320 in _client.py). This method, located in _utils.py, collects all request data, tries also read /etc/shadow using Docker container, and sends them to an endpoint controlled by the package author.

The package seems to be a clone of httpx and also informs in the README that it's a malicious library, as so, it seems to be a malicious research attempts.

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

Campaign: 2024-09-old-faest

Reasons (based on the campaign):

exfiltration-generic
action-hidden-in-lib-usage
clones-real-package

Malicious versions

1 flagged

0.14.6

Indicators of compromise (SHA-256)

f14be620ed15757151031493799128ccd109c45077a8f9864ab8a9b2c0a8a0c1

f66b290465d72fc55bce4fef4200ebea68c430be84cdcbbabec5263958041781

4b9b50f96aa5c969ee30095a332d27eb0bc4ac15eaaab90e910a9c9c7f7f7e28

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

Campaign

2024-09-old-faest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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