offensive-container-escape skillA
offensive-container-escape is agent-read markdown (skill) from snailsploit/claude-red: Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAP_SYS_ADMIN, CAP_SYS_PTRACE, and CAP_NET_ADMIN, cgroup v1 notify_on_release escape, runc CVEs such as CVE-2019-5736 and CVE-2024-21626 Leaky Vessels, kernel exploits from within containers, and Dockerfile misconfigurations like --privileged.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Container Escape and Breakout You have a shell inside a container. Your objective is to break out to the underlying host operating system. Container isolation relies on Linux namespaces, cgroups, seccomp profiles, AppArmor/SELinux, and dropped capabilities. Every misconfiguration in these layers is an escape vector. This skill walks you through systematic enumeration, exploitation of common misconfigurations, abuse of exposed runtime sockets, capability-based escapes, cgroup breakouts, and known CVEs against container runtimes. ## Quick Workflow 1. Confirm you are inside a container (check for `.dockerenv`, cgroup entries, PID 1 process). 2. Enumerate capabilities, mounts, namespaces, and sockets with automated tools. 3. Identify the escape vector: privileged mode, socket exposure, dangerous capabilities, cgroup misconfiguration, or vulnerable runtime. 4. Execute the breakout technique matching the vector. 5. Validate host access by reading `/etc/hostname`, checking PID namespace, or writing to host filesystem. 6. Pivot from host access to lateral movement across the cluster or infrastructure. --- ## Phase 1: Container Detection and Enumeration …
Read the whole file at its exact version.
How to install
mdr add snailsploit/claude-red/offensive-container-escape@git:20260825.8cffe5dmdr add snailsploit/claude-red/offensive-container-escape@sha256:0646139103a2be51Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_jv6iydhycbpgg5wz)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (21739 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
snailsploit/claude-red · 6,831 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jv6iydhycbpgg5wz GET https://markdownregistry.com/api/v1/resolve?ref=snailsploit/claude-red/offensive-container-escape GET https://markdownregistry.com/api/v1/blob/0646139103a2be51f4f6875e1bdf53cd00c23e259ee47e0262dc2fd0c38cb4fc
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from snailsploit/claude-red
Every file in snailsploit/claude-red