Malicious Kubernetes Node Escape via chroot to Node kubectl Path

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-10-16
Updated
2026-10-16

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 chroot into the node-local kubectl directory used on managed Kubernetes nodes, a container-to-node escape technique observed in real-world cluster attacks after landing in a privileged pod. Breaking out to the node host filesystem gives the attacker control over the worker node and any credentials stored on it.

Related detections9 linkedT1611 — drag to rearrange
Suspicious Kubernetes Pod Deployment with Privileged or Host Namespace Flags
Suspicious Privileged or Host Namespace Kubernetes Pod Creation
Malicious Privileged Container Creation in Kubernetes (via audit)
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 Kubernetes Node Escape via chroot to Node kubectl Path
Pivot detection · T1611 · 9 related

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