Which versions of fuckingnuker are malicious?

The following PyPI versions of fuckingnuker are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate fuckingnuker if I installed it?

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

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

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

Malicious package

fuckingnukerPyPI

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

MAL-2025-47766

Immediate action

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

pip uninstall fuckingnuker

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.3

Indicators of compromise (SHA-256)

60c6ba56e3bdcbf2452eaa3bc65fcafb887f16644430b4fcfcde0b17a1f5fdab

44afe54295548ec96b34a7528f869c1ca61b58b2c6f35a08bfe7b44c4bc959a7

ca3eb102d38e2886117259b723d471865369ed7f6b971d10d59e178eae813adb

8ab227935035811a2d20938b0084881dd150031bd03d7aaae9263c0132beab97

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

Campaign

RLMA-2025-047672025-08-k7eelRLUA-2026-00335

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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