Suspicious Docker Socket Access via curl Unix Socket for Container Escape

PremiumReviewedSigma · High · v1
Category
process_creation
Author
HuntRule
Published
2026-10-19
Updated
2026-10-19

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects curl talking to the Docker daemon over its Unix socket to create or start containers, a technique used to escape a container by spawning a privileged sibling with the host filesystem mounted. Direct access to docker.sock grants effective root on the node. Detecting this exposes an attempted breakout through the exposed Docker API.

Related detections9 linkedT1611 — drag to rearrange
Suspicious Kubernetes Pod Deployment with Privileged or Host Namespace Flags
Malicious Kubernetes Node Escape via chroot to Node kubectl Path
Suspicious Privileged or Host Namespace Kubernetes Pod Creation
Malicious Container Escape via Privileged Docker Host PID Namespace
Malicious Privileged Container Creation in Kubernetes (via audit)
Malicious Docker Socket Access via Curl Unix Socket
Suspicious Cgroup release_agent Abuse for Container Escape
Suspicious Privileged Docker Container Launch With Host chroot
Malicious Direct etcd Write to Kubernetes Registry via ETCDCTL_API (via process_creation)
Suspicious Docker Socket Access via curl Unix Socket for Container Escape
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.