Which versions of nukeport are malicious?

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

How do I remediate nukeport if I installed it?

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

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

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

Malicious package

nukeportPyPI

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

MAL-2025-47791

Immediate action

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

pip uninstall nukeport

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)

63896e2ce24e7e714f0431db8aebbc4327ad614d0cb8075ca1b9aa97fff2fa8d

a43fd77701a95c288ae60c5f7eb9d4f6822a2eb82cc0018b0c171be585271e96

93c339ed9593cfb15c4c9907ec2e2d10c4e7f7acc0fb1acca50cb81d157b0551

aeed8c3e1ebcd335eaa638fd232f484192bca812c355c067a1de032a4a4ec4f9

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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