cloud-kubernetes
Attack exposed Kubernetes: API server, kubelet, etcd, dashboards, and RBAC. Load on k8s signals — ports 6443/10250/2379/8443, /api/v1, kube-dns, a pod foothold, or "kubernetes/k8s". Signals: kubectl, service-account tokens, exposed dashboard, container in a cluster.
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/cloud-kubernetesWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagea62809f5…34176229
a62809f58d13…000a341762291 file · 1.3 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-kubernetes@ee0e0c5
On this page
When it applies
A Kubernetes control-plane or node component is reachable (externally or from a pod foothold), or you landed in a container inside a cluster and want to escalate to cluster admin / other tenants.
Why it works
k8s exposes powerful HTTP APIs that are frequently unauthenticated or over-permissioned: anonymous API access, kubelet read/exec on 10250, unauth etcd (all secrets), and mounted service-account tokens with broad RBAC. One over-scoped token = cluster takeover.
Method
- From outside:
kube-hunter; probe API server 6443 (/api/v1anonymous), kubelet 10250 (/pods,/runexec), etcd 2379 (keys→secrets), and exposed dashboards (8443/anonymous). - From a pod: read the mounted token
/var/run/secrets/kubernetes.io/serviceaccount/;kubectl auth can-i --listto see what it grants. - Escalate via RBAC: over-permissioned SA → create/exec pods, read secrets across namespaces,
or
create podswith a hostPath/privileged spec to mount the node (→ node/cluster takeover). - Container→node breakout: privileged pod, hostPID/hostNetwork, or a hostPath mount to the
host filesystem (→
cloud-container-escape). - Loot:
kubectl get secrets -A, cloud IAM via node metadata (→cloud-imds-ssrf).
Gotchas
kubectl auth can-i --listfirst — it tells you exactly what the token can do; don't guess.- Anonymous API/kubelet is common in labs and misconfigured clusters — always test unauth.
- On bug bounty, prove access read-only where possible; creating privileged pods is high-impact — mind RoE.
Verify success
Cluster-level access proven: reading secrets across namespaces, exec into others' pods, or node filesystem/cloud-creds access from an over-scoped token.
References
kube-hunter/peirates; NCC "Kubernetes security"; MITRE ATT&CK Containers.
Files in this version
- SKILL.md2.4 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | a62809f5 | Signed | – |
More from NoorQureshi
All from this publisherMore in Linux, cloud and containers
See the category- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login