Individual skill
offensive-k8s-attacks
Kubernetes cluster attack techniques covering the full attack lifecycle from initial foothold in a pod to cluster-wide compromise. Covers service account token theft and impersonation, RBAC misconfiguration exploitation including wildcard permissions and privilege escalation via role binding, direct etcd access for secret extraction, kubelet API abuse on port 10250 and read-only port 10255, pod escape via hostPID hostNetwork and hostPath volume mounts, Kubernetes secrets enumeration and decoding, admission controller bypass techniques, network policy bypass and lateral movement, cloud metadata service access from pods for credential theft on AWS EKS GCP GKE and Azure AKS, CRD and operator abuse for persistence, and node compromise via DaemonSet deployment. Tools include kubectl, kube-hunter, peirates, kubeaudit, kdigger, kubeletctl. Maps to MITRE ATT&CK T1609 Container Administration Command, T1610 Deploy Container, T1613 Container and Resource Discovery. Use this skill when assessing Kubernetes clusters, attacking from within a compromised pod, exploiting RBAC or kubelet misconfigurations, or performing cloud-native lateral movement.
Skills/container/offensive-k8s-attacks/SKILL.md
Source commit a8de813edc9f66f60d44cfe42d47750e89d9930b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 10,505
- Repository last updated
- Oct 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-ai Repository topic
- claude-skills Repository topic
- redteam Repository topic
- redteam-tools Repository topic
- skills Repository topic
- claude-pt Repository topic
- devops Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytesSKILL.mdcore · 27,489 bytes
Read excerpt
# Kubernetes Cluster Attacks
You have access to a Kubernetes environment, either through a compromised pod, stolen kubeconfig, or exposed API server. Your objective is to escalate privileges, move laterally, and compromise the cluster or underlying cloud infrastructure. Kubernetes security depends on RBAC policies, network policies, admission controllers, pod security standards, and cloud IAM integration. Each misconfiguration opens a path to deeper access. This skill covers systematic enumeration, privilege escalation, secret extraction, and cluster-wide compromise techniques.
## Quick Workflow
1. Determine your initial position: pod shell, stolen token, exposed API, or kubeconfig file.
2. Enumerate service account permissions, cluster roles, and accessible resources.
3. Identify escalation vectors: RBAC gaps, kubelet exposure, hostPath mounts, cloud metadata access.
4. Escalate privileges by chaining misconfigurations or abusing overprivileged service accounts.
5. Extract secrets, pivot to other namespaces, and target the control plane.
6. Leverage cloud metadata or etcd access for infrastructure-wide compromise.
---