Which versions of fuckyoubitchbro are malicious?

The following PyPI versions of fuckyoubitchbro are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate fuckyoubitchbro if I installed it?

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

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

Yes — fuckyoubitchbro is associated with the 2025-08-k7eel 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 fuckyoubitchbro across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fuckyoubitchbro (version 0.1.1).

Part of a larger attack: 2025-08-k7eel published 31 malicious packages. See the full campaign →

Malicious package

fuckyoubitchbroPyPI

Advisory published Aug 30, 2025Updated Dec 3, 2025

fuckyoubitchbro is a confirmed malicious PyPI package (MAL-2025-191736) that steals credentials and exfiltrates sensitive data (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fuckyoubitchbro (PyPI)

MAL-2025-191736

Immediate action

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

pip uninstall fuckyoubitchbro

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

e3752f0763bfa22798f1c85005d73c69f222d320c0a2b7e45f72fe1989e1c29b

fbbf1ade5d81c12afb87a44117b27f76d2e4bfa91b578fc50dfb44a8bb79cabe

Detection & response playbook

Credential / info stealer

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

Campaign

2025-08-k7eel

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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