Which versions of fucknukeer are malicious?

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

How do I remediate fucknukeer if I installed it?

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

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

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

Malicious package

fucknukeerPyPI

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

MAL-2025-47767

Immediate action

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

pip uninstall fucknukeer

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)

25d7222821e618a5b5fa3449495c4a362bc362b4751cc9631095b61c06b7f116

b596fd0775d468a0ec07984c4fcaa75dbbf55c4bc5b4fd8672db69907de0ca59

ba298ecb23601a4d9ddb1c2123c99ed19ff6a44c82225c5627a97033225feabb

c944fb566f557558a85de9c3cedffbf45ba9290526956abb4aa88265813b3553

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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