Malicious Privileged Container Creation in Kubernetes (via audit)

PremiumReviewedSigma · High · v1
Product
kubernetes
Service
audit
Author
HuntRule
Published
2026-09-05
Updated
2026-09-05

ATT&CK techniques

Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects a Kubernetes API request that creates a pod with a privileged security context, which grants the container near-host capabilities and is a primary path for escaping to the underlying node. Container escape and privileged workloads are emerging techniques in the Red Canary Threat Detection Report as adversaries target cloud-native environments. Detecting privileged pod creation surfaces a high-risk configuration that enables host compromise.

Related detections6 linkedT1611 — drag to rearrange
Malicious Docker Socket Access via Curl Unix Socket
Suspicious Cgroup release_agent Abuse for Container Escape
Malicious Direct etcd Write to Kubernetes Registry via ETCDCTL_API (via process_creation)
Malicious Container Escape via core_pattern Hijack (via process_creation)
Kubernetes Pod Created With hostPath Volume Mount
Kubernetes Privileged Pod Created via Pod Creation Requests
Malicious Privileged Container Creation in Kubernetes (via audit)
Pivot detection · T1611 · 6 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.