Which versions of kube-health-tools are malicious?

The following PyPI versions of kube-health-tools are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.14, 2.0.0. Treat any of these as compromised.

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

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

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

Yes — kube-health-tools 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-health-tools 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-health-tools (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kube-health-tools across your stack and pipelines.

Malicious package

kube-health-toolsPyPI

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

MAL-2026-2327

Immediate action

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

pip uninstall kube-health-tools

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

15 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.81.0.91.0.101.0.111.0.121.0.131.0.142.0.0

Indicators of compromise (SHA-256)

4d36d5ed9b1bc15c12e89f48c1228a4f6e3aebe558a67d535655e280b25b4440

7e538c73cef5f37655f767c9b0c0bafcc0e41875243137f5d9bc6226a49bf7d9

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-health-tools (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kube-health-tools across your stack and pipelines.
If you installed it — respond
kube-health-tools 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-health-tools 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-health-tools 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-health-tools on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.8, and 7 more 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-health-tools-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