Malicious Docker Socket Access via Curl Unix Socket

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-07-17
Updated
2026-08-28

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 curl invocations that talk directly to the Docker daemon Unix socket, the technique an AI agent-driven actor used to create a privileged container and escape onto the host orchestration plane. Direct API calls to the docker.sock allow spawning containers that mount the host filesystem. This behavior is a strong container escape indicator.

Related detections6 linkedT1611 — drag to rearrange
Malicious Privileged Container Creation in Kubernetes (via audit)
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 Docker Socket Access via Curl Unix Socket
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.