detecting-container-escape-attempts

Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators

Jump to install

Repository: xalgord/xalgorix
Last source activity: June 6, 2026 at 16:41
Detected SKILL.md language: English
Stars: 813
Forks: 146

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/xalgord/xalgorix --skill detecting-container-escape-attempts

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

View all from this repository

Detecting Container Escape Attempts

Overview

Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators such as namespace manipulation, capability abuse, kernel exploits, mounted sensitive paths, and anomalous syscall patterns using runtime security tools like Falco, Sysdig, and custom seccomp/audit rules.

When to Use

When investigating security incidents that require detecting container escape attempts

When building detection rules or threat hunting queries for this domain

When SOC analysts need structured procedures for this analysis type

When validating security monitoring coverage for related attack techniques

Detection Gaps & Validation

Name-based rules are bypassable: rules keyed on proc.name in (nsenter, unshare, mount) are evaded by copying the binary to another name or statically compiling it. Where possible match on evt.type = setns/unshare/mount syscalls, not process names.

proc.is_exe_upper_layer and container.privileged can be unreliable under containerd; a pod with hostPID: true + nsenter -t 1 or a hostPath mount of / escapes without tripping namespace-syscall rules because the mount happens at admission, not runtime.

CAP_SYS_ADMIN without privileged: true: an escape via added capability (cgroup release_agent, mount) won't match a container.privileged=true condition - detect on the capability and the syscall.

Seccomp SCMP_ACT_LOG only logs, it does not block; confirm the profile is actually attached (docker inspect ... SecurityOpt).

release_agent / notify_on_release paths vary by cgroup v1 vs v2 mount location - a contains release_agent match can miss the v2 path.

How to validate the rules fire: run falcosecurity/event-generator run syscall --action PtraceAttachContainer, plus a test pod that cat /etc/shadow, writes /proc/sysrq-trigger, and runs nsenter; grep kubectl logs -n falco-system -l app.kubernetes.io/name=falco for the CRITICAL escape rules.

Detecting Container Escape Attempts

Overview

When to Use

When investigating security incidents that require detecting container escape attempts

When building detection rules or threat hunting queries for this domain

When SOC analysts need structured procedures for this analysis type

When validating security monitoring coverage for related attack techniques

Detection Gaps & Validation

Seccomp SCMP_ACT_LOG only logs, it does not block; confirm the profile is actually attached (docker inspect ... SecurityOpt).

release_agent / notify_on_release paths vary by cgroup v1 vs v2 mount location - a contains release_agent match can miss the v2 path.

# /etc/falco/rules.d/container_escape.yaml # Detect container escape via privileged container - rule: Container Escape via Privileged Mode desc: Detect attempts to escape container using privileged capabilities condition: > spawned_process and container and (proc.name in (nsenter, unshare, mount, umount, modprobe, insmod) or (proc.name = chroot and proc.args contains "/host")) output: > Container escape attempt via privileged operation (user=%user.name container=%container.name image=%container.image.repository command=%proc.cmdline pid=%proc.pid %container.info) priority: CRITICAL tags: [container, escape, T1611] # Detect Docker socket access from container - rule: Container Access to Docker Socket desc: Detect container reading/writing to Docker socket condition: > (open_read or open_write) and container and fd.name = /var/run/docker.sock output: > Docker socket accessed from container (user=%user.name container=%container.name image=%container.image.repository fd=%fd.name command=%proc.cmdline %container.info) priority: CRITICAL tags: [container, escape, docker_socket] # Detect sensitive proc filesystem access - rule: Container Access to Sensitive Proc Paths desc: Detect container accessing host-sensitive proc paths condition: > open_read and container and (fd.name startswith /proc/sysrq-trigger or fd.name startswith /proc/kcore or fd.name startswith /proc/kmsg or fd.name startswith /proc/kallsyms or fd.name startswith /sys/kernel) output: > Sensitive proc/sys access from container (user=%user.name container=%container.name path=%fd.name command=%proc.cmdline %container.info) priority: CRITICAL tags: [container, escape, proc_access] # Detect cgroup escape technique - rule: Container Cgroup Escape Attempt desc: Detect writing to cgroup release_agent (escape technique) condition: > open_write and container and (fd.name contains release_agent or fd.name contains notify_on_release) output: > Cgroup escape attempt detected (user=%user.name container=%container.name path=%fd.name command=%proc.cmdline %container.info) priority: CRITICAL tags: [container, escape, cgroup] # Detect kernel module loading from container - rule: Container Loading Kernel Module desc: Detect container attempting to load kernel modules condition: > spawned_process and container and (proc.name in (modprobe, insmod, rmmod) or (evt.type = init_module or evt.type = finit_module)) output: > Kernel module load attempt from container (user=%user.name container=%container.name command=%proc.cmdline %container.info) priority: CRITICAL tags: [container, escape, kernel_module] # Detect namespace manipulation - rule: Container Namespace Manipulation desc: Detect setns/unshare syscalls from container condition: > container and (evt.type = setns or evt.type = unshare) and not proc.name in (containerd-shim, runc) output: > Namespace manipulation from container (user=%user.name container=%container.name syscall=%evt.type command=%proc.cmdline %container.info) priority: CRITICAL tags: [container, escape, namespace] # Detect mount operations from container - rule: Container Mount Sensitive Filesystem desc: Detect container mounting host filesystems condition: > spawned_process and container and proc.name = mount and (proc.args contains "/dev/" or proc.args contains "proc" or proc.args contains "sysfs") output: > Sensitive mount operation from container (user=%user.name container=%container.name command=%proc.cmdline %container.info) priority: HIGH tags: [container, escape, mount]

name	detecting-container-escape-attempts
description	Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators
domain	cybersecurity
subdomain	container-security
tags	["containers","kubernetes","docker","security","runtime-security","escape-detection"]
version	1.0
author	mahipal
license	Apache-2.0
d3fend_techniques	["Platform Monitoring","Process Code Segment Verification","Stack Frame Canary Validation","Segment Address Offset Randomization","Process Analysis"]
nist_csf	["PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01"]

name	detecting-container-escape-attempts
description	Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators
domain	cybersecurity
subdomain	container-security
tags	["containers","kubernetes","docker","security","runtime-security","escape-detection"]
version	1.0
author	mahipal
license	Apache-2.0
d3fend_techniques	["Platform Monitoring","Process Code Segment Verification","Stack Frame Canary Validation","Segment Address Offset Randomization","Process Analysis"]
nist_csf	["PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01"]

Vector	Technique	MITRE ID
Privileged containers	Mount host filesystem, load kernel modules	T1611
Docker socket mount	Create privileged container from within	T1610
Kernel exploits	CVE-2022-0185 (fsconfig), Dirty Pipe, runc CVEs	T1068
Capability abuse	CAP_SYS_ADMIN, CAP_SYS_PTRACE, CAP_NET_ADMIN	T1548
Sensitive mounts	/proc/sysrq-trigger, /proc/kcore, cgroup release_agent	T1611
Namespace escape	nsenter, unshare to host namespaces	T1611
Symlink/bind mount	Escape through /proc/self/root	T1611

detecting-container-escape-attempts

Install options

Review the source files