Which versions of kube-node-health are malicious?

The following PyPI versions of kube-node-health are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate kube-node-health if I installed it?

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

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

Yes — kube-node-health is associated with the 2026-03-kube-health-tools 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 kube-node-health 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 kube-node-health (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kube-node-health across your stack and pipelines.

Malicious package

kube-node-healthPyPI

Malicious code in kube-node-health (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2400

Immediate action

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

pip uninstall kube-node-health

What this malware does

During import, the code download and starts remote executable that later connects to a C2 server, likely establishing a reverse tunnel. After executing the remote binary, the code performs covering-tracks actions by removing the binary from disk, and - depending on version - modifying the package code. The dropper code is either a Python script, or a compiled binary with obfuscated location of the remote binary and config for it.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-kube-health-tools

Reasons (based on the campaign):

Downloads and executes a remote executable.
backdoor
obfuscation
covering-tracks

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

391555cff14c82156843bee267daf896c3e3e989b9c899ef34b12ac7e23b1c7e

4777264b720c2b41fc408aea73a5f6968b36bbc5cc8f621cf2e7feed750f7421

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

Campaign

2026-03-kube-health-tools

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks kube-node-health-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