Malicious Privileged Container Spawn via Docker Socket (via process_creation)

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-11-05
Updated
2026-11-05

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  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 interaction with the Docker unix socket to create a privileged container, a container-escape technique highlighted in the BrokenSesame research. Access to the mounted docker.sock lets an attacker launch a privileged container that mounts the host filesystem. This combination indicates an attempt to break isolation and reach the node.

Related detections9 linkedT1610 — drag to rearrange
Suspicious IngressNightmare NGINX Ingress Controller Spawning Shell (CVE-2025-1974)
Suspicious Helm Tiller Unauthenticated Access on Port 44134
Possible IngressNightmare Exploitation via NGINX Loading Shared Object From Proc (CVE-2025-1974)
Suspicious Docker Container Spawning Remote Script Download (via process_creation)
Suspicious Docker Socket Access via curl Unix Socket for Container Escape
Suspicious Kubernetes Pod Deployment with Privileged or Host Namespace Flags
Malicious Container Escape via Privileged Docker Host PID Namespace
Suspicious Privileged Docker Container Launch With Host chroot
Malicious Docker Client Targeting Remote Exposed 2375 API
Malicious Privileged Container Spawn via Docker Socket (via process_creation)
Pivot detection · T1610 · 9 related

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