Which versions of nukebount are malicious?

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

How do I remediate nukebount if I installed it?

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

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

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

Malicious package

nukebountPyPI

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

MAL-2025-47789

Immediate action

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

pip uninstall nukebount

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)

37c0773f023978da1d2d4f82385cdecb97177a074b534fadf6a409f0724cb0f9

b1bd68dd85f643f501baaa7fda8c3924013ce9a1cb6648b50ed323f4d25e2d84

08b5c0de8042d5eedece216ff03327fbb71f32994257141f7d47f01aa8aa5491

3886226e20268f34a29be79d2246aba4e65b4318afb1f81f9914af8dff96fe8c

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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