container-escape-techniques
Fail
Audited by Gen Agent Trust Hub on Sep 26, 2026
Risk Level: HIGHPERSISTENCECOMMAND_EXECUTIONDATA_EXFILTRATIONREMOTE_CODE_EXECUTIONPRIVILEGE_ESCALATIONEXTERNAL_DOWNLOADS
Full Analysis
- [PERSISTENCE]: Instructions for maintaining access to the host post-escape.
- Evidence in
DOCKER_ESCAPE_CHAINS.md: Adding an SSH key to/root/.ssh/authorized_keys. - Evidence in
DOCKER_ESCAPE_CHAINS.md: Creating a reverse shell cron job in/etc/crontab. - [COMMAND_EXECUTION]: Provides sequences for full host namespace breakout.
- Evidence in
SKILL.md: Usingnsenterto access host namespaces from a privileged container. - Evidence in
SKILL.md: Direct mounting of host physical disks to access the host filesystem. - [DATA_EXFILTRATION]: Explicit commands to harvest sensitive system credentials.
- Evidence in
SKILL.mdandDOCKER_ESCAPE_CHAINS.md: Instructions to read/etc/shadowfrom the host. - [REMOTE_CODE_EXECUTION]: Patterns for establishing attacker-controlled remote shells.
- Evidence in
DOCKER_ESCAPE_CHAINS.md: Presence of bash reverse shell one-liners targeting remote IPs. - Evidence in
SKILL.md: Python scripts usingctypesfor root process injection. - [PRIVILEGE_ESCALATION]: Methods for bypassing container security boundaries.
- Evidence in
SKILL.md: Exploitation ofCAP_SYS_ADMIN,CAP_SYS_PTRACE, andCAP_DAC_READ_SEARCH(Shocker exploit). - [EXTERNAL_DOWNLOADS]: Recommends downloading and running third-party security tools.
- Evidence in
SKILL.md: Links to tools likedeepce.sh,CDK, andamicontainedfor automated exploitation.
Recommendations
- AI detected serious security threats
Audit Metadata