kube-hunter
kube-hunter looks for security weaknesses in Kubernetes clusters from an attacker's perspective. (The project README notes that it is in maintenance mode and points to newer tooling; check the repository before relying on it.)
Legal & ethical use. Use this tool only on systems, networks and data that you own or have explicit written permission to test. Unauthorised access or scanning can break computer-misuse laws (for example Pakistan's Prevention of Electronic Crimes Act, 2016, and equivalents elsewhere). Practise in your own lab or in authorised environments such as CTFs.
What it is used for
- Check a lab cluster for exposed components
- Learn common Kubernetes misconfigurations
Key features
- Passive and active hunting modes
- Remote and in-cluster scanning
- Report output
Installation
See the repository README for pip, Docker and in-cluster options.
Beginner usage guide
Run in passive mode first against a lab cluster you own and review the findings.
Example commands
Run these only against your own lab or authorised targets. Placeholder addresses such as 192.0.2.x are documentation ranges.
Passive remote scan (lab)
kube-hunter --remote 192.0.2.40Scans the given cluster address; run only against clusters you own.
References
Source verification
Last reviewed: 2026-10-27
Links checked over HTTP: 2026-10-27 07:51 UTC — official: 200, docs: 200, repo: 200
Commands were written from the official documentation and have not been executed on this site; test them in your lab.