Which versions of fuckyoubitch are malicious?

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

How do I remediate fuckyoubitch if I installed it?

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

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

Yes — fuckyoubitch is associated with the RLMA-2025-04771, 2025-08-k7eel, RLUA-2026-00339 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 fuckyoubitch 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 fuckyoubitch (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fuckyoubitch across your stack and pipelines.

Malicious package

fuckyoubitchPyPI

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

MAL-2025-47770

Immediate action

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

pip uninstall fuckyoubitch

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)

5c1a3fb620184918136ffb0f7ef1c0ff04dfe5a81b4b4d59e0ca796c56e168c6

832d4ed53fb19c8a416bde9c4ded680f553be7bc211f6cc6e557491a0eaf305a

d4b44b0fb797b54e70ce9da891342e05380f0a6aa9ff1c8fb43a3a65e7babe97

581eedd691545611165972b1bddb97aa84e23b259da34b7605ecc85e3f306346

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 fuckyoubitch (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fuckyoubitch across your stack and pipelines.
If you installed it — respond
fuckyoubitch 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 fuckyoubitch 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 fuckyoubitch 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. fuckyoubitch 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

RLMA-2025-047712025-08-k7eelRLUA-2026-00339

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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