Which versions of fucknukerbro are malicious?

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

How do I remediate fucknukerbro if I installed it?

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

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

Yes — fucknukerbro is associated with the RLMA-2025-04770, 2025-08-k7eel, RLUA-2026-00338 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 fucknukerbro 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 fucknukerbro (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 fucknukerbro across your stack and pipelines.

Malicious package

fucknukerbroPyPI

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

MAL-2025-47769

Immediate action

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

pip uninstall fucknukerbro

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)

01e71e4d05b022d8b00e51d07fddbe16ad57355abe04deea52eb311bb3ea49ae

09ab5d8ef7226ee9c3c4ecf42475e6d903c5d332075b8fbf504c5d62c7639f29

9cf00cbb3858ebd2227a86195c621a7f8ca9675a11e80de401d0d1b05c5f13f6

53b02dccf4c8628a4cfc210cd07e8c12dfa8d3bb21fb3e39cc4eb19194cbf731

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 fucknukerbro (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 fucknukerbro across your stack and pipelines.
If you installed it — respond
fucknukerbro 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 fucknukerbro 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 fucknukerbro 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. fucknukerbro 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-047702025-08-k7eelRLUA-2026-00338

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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