# Khaos Socat Operations

> Use socat only on observed in-scope non-HTTP service ports to relay raw TCP/UDP; it performs no protocol-level analysis and requires explicit scope authorization for non-web services.

- Skill: `henriqqw/khaos-socat-operations` (Agent Skill)
- Install (CLI): `npx get-skill add henriqqw/khaos-socat-operations`
- Raw SKILL.md: https://api.skillmd.com/api/skills/henriqqw/khaos-socat-operations/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: henriqqw (https://skillmd.com/u/henriqqw)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/henriqqw/khaos-socat-operations

---


# Operacao do socat no Khaos

O adapter Khaos executa socat no modo `- TCP:<host>:<port>,crnl,connect-timeout=5` para relay de stdin↔TCP em uma unica porta de servico observada. Nao realiza varredura, nao faz fuzzing e nao move lateralmente.

## Pre-condicoes obrigatorias

- **Stage da task:** `enumeration` ou `exploitation`.
- **Porta de servico:** porta observada explicitamente no scope (nao-HTTP/HTTPS).
- **Estado do assessment:** `executing_stage`.
- O assessment deve ter `network_enabled: true` no authorization plan.
- **Atencao:** socat so e util em servicos de texto (SMTP, FTP, POP3, telnet, protocolos customizados). Em HTTP/HTTPS use httpx ou katana.

## Fluxo correto de execucao

```
1. POST /assessments/{id}/operator/tasks/{taskId}/claim
   {"owner": "<owner>", "lease_seconds": 120}

2. POST /assessments/{id}/operator/events
   {"event": "action_proposed", "data": {
     "action_id": "<uuid-novo>",
     "task_id":   "<taskId>",
     "owner":     "<owner>",
     "tool_id":   "socat",
     "title":     "socat TCP probe: <host>:<port>"
   }}

3. POST /assessments/{id}/operator/events
   {"event": "action_decision", "data": {
     "action_id": "<mesmo-uuid>",
     "task_id":   "<taskId>",
     "owner":     "<owner>",
     "tool_id":   "socat",
     "allowed":   true
   }}

4. POST /tools/socat/run
   {"target_id": "<id>", "assessment_id": "<id>",
    "endpoint_url": "<url-com-porta>",
    "execute": true, "confirm": true,
    "action_id": "<mesmo-uuid>", "task_id": "<taskId>", "owner": "<owner>"}
```

O adapter deriva `host:port` do `socatPort` calculado a partir da URL observada (porta explicita ou padrao de esquema).

## Interpretar sem superafirmar

| Resultado | Interpretacao |
|---|---|
| Banner recebido | Servico ativo na porta; usar banner para fingerprinting manual |
| Conexao recusada | Porta fechada ou filtrada |
| Timeout | Firewall stateful ou porta filtrada silenciosamente |

A saida bruta de socat nao e um finding. Use as evidencias para formular hipoteses de vulnerabilidade (banner disclosure, auth bypass em protocolo de texto).

