Which versions of fucknuker are malicious?

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

How do I remediate fucknuker if I installed it?

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

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

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

Malicious package

fucknukerPyPI

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

MAL-2025-47768

Immediate action

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

pip uninstall fucknuker

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)

1487da5d82865356432a7bffbf42b7a0f172e2f79d2d24992713c89e56b829c5

f727f85ef3f356a863be8eb1e2b91d1f0e041d25573e7ca2c9127c5647d12e08

ef4a800b6c8d046529d8fdc3a49314fa87c84e2cc8b499b3c2c1941d7103c5fe

b92498769eff58b696ace7f66343dd12cf081f69a8847671a24d7b6841986afc

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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