# Khaos Scope Recon

> name: khaos-scope-recon

- Skill: `henriqqw/khaos-scope-recon` (Agent Skill)
- Install (CLI): `npx get-skill add henriqqw/khaos-scope-recon`
- Raw SKILL.md: https://api.skillmd.com/api/skills/henriqqw/khaos-scope-recon/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-scope-recon

---

﻿---
name: khaos-scope-recon
description: Build a traceable asset and endpoint inventory for an authorized bug bounty program before active testing.
metadata:
  khaos:
    tool_ids: [subfinder, httpx, gau, waybackurls, katana, nmap]
    wordlist_ids: [pkgforge-api-tiny, pkgforge-dns-tiny]
    stages: [recon, enumeration]
    source_type: derived
    source:
      repository: https://github.com/uphiago/recon-skills
      revision: 1260244136edc6ae698d76d3d526f503e322778d
      path: recon/web-enumeration/SKILL.md
      license: MIT
      reviewed_by: Khaos maintainers
      review_note: Adaptado para ativos explicitamente autorizados; descoberta nunca amplia escopo.
---

# Escopo e reconhecimento

Use esta skill quando o operador precisar transformar as regras de um programa em um inventário verificável. Comece pela versão e data das regras, ativos incluídos e excluídos, métodos permitidos, limite de taxa e contas de teste. Dados de escopo de terceiros, como `bounty-targets-data`, são pistas para revisão; nunca equivalem a autorização atual.

1. Registre cada raiz, subdomínio, URL e IP com fonte, data de observação e relação com uma regra explícita. Não promova um host descoberto a alvo ativo sem resolver essa relação.
2. Faça descoberta passiva e deduplique por hostname normalizado. Consulte DNS e HTTP apenas dentro do escopo e do orçamento de requisições. Uma resposta de CDN, redirecionamento ou wildcard não prova propriedade do ativo.
3. Classifique endpoints por origem: navegação observada, especificação OpenAPI, JavaScript, arquivo histórico ou ferramenta. Mantenha método, parâmetros, autenticação, status e evidência bruta. Marque URL histórica como candidata até reproduzir sua existência.
4. Antes de portas, crawling ou fuzzing, verifique as regras para esses métodos e os limites do projeto. Execute uma amostra pequena; interrompa se houver erros em série, bloqueio, impacto operacional ou mudança de escopo.
5. Entregue mapa de ativos e fila de hipóteses priorizada por exposição e relevância. Inclua falsos positivos descartados e limites da cobertura.

Para um fluxo de descoberta em várias etapas, mantenha a linhagem `fonte passiva → resolução/HTTP → porta → serviço → template → conteúdo`. Antes de passar à etapa seguinte, registre quais entradas ainda estão em escopo, quais foram descartadas e qual limite de taxa foi aprovado. Deduplique nomes e endereços para análise, mas não converta automaticamente escopo por domínio em permissão de varrer os IPs compartilhados que ele resolve. Título de página e ausência de marca de CDN são indícios insuficientes de que um IP seja origem controlada pelo programa.

Ao revisar Nmap, Nuclei e ffuf, trate XML, resultados de template e status 200/403 como pistas. Compare tipo de conteúdo, tamanho, palavras e resposta de controle para separar página de erro genérica de recurso real. A ordem e os comandos do [fluxo de fuzzing e scanning](https://infosecwriteups.com/a-practical-workflow-for-fuzzing-and-scanning-in-bug-bounty-64fa00ded29b) foram lidos no texto fornecido pelo operador; as taxas e os scans de centenas de IPs citados no artigo não são valores padrão desta skill.

As listas de dorks e palavras externas devem ser revisadas, reduzidas e atribuídas ao repositório e commit antes do uso. Evite importar listas de senhas ou milhões de entradas para a rotina de descoberta. O artigo de [reconhecimento de API](https://infosecwriteups.com/how-to-discover-api-subdomains-api-hacking-41ef91d00846) embasa o contraste entre versões e serviços; a [lista de recon](https://infosecwriteups.com/recon-to-master-the-complete-bug-bounty-checklist-95b80ea55ff0) ficou acessível apenas em parte. Consulte o [registro de fontes](../../../../../docs/research/2026-10-13-source-audit.md) para o nível de leitura.

## Detecção de WAF e Proxy

Quando o alvo usa Cloudflare ou outro WAF com rate-limiting agressivo:
- Após ~15 requisições, respostas 403 com 9 bytes (`Forbidden` em texto plano) indicam rate-limiting por IP
- Header `CF-RAY` presente na resposta = Cloudflare; `Server: cloudflare` confirma
- Solução: configure o proxy pool antes de iniciar a fase de enumeration (ver skill `khaos-proxy-evasion`)
- Use `bootstrap_seed_endpoint: true` no authorization plan para evitar o problema chicken-and-egg de endpoint verificado: sem endpoint verificado não há como fazer a primeira requisição via Khaos, e sem a primeira requisição não há endpoint verificado
## BugHunter Patterns

*Patterns sourced from [elementalsouls/Claude-BugHunter](https://github.com/elementalsouls/Claude-BugHunter/tree/main/skills/recon-scope-triage/SKILL.md)*

## When to use this skill

Trigger when:
- The target brand is a common/dictionary word or shared term (e.g. `apex`, `summit`, `vertex`, `nova`, `core`, `orbit`, `pulse`, `unity`…)
- You receive an ASM report, recon export, breach combo, repo list, bucket list, or mobile-app list to act on
- A "Critical" count looks implausibly high (hundreds) for the org's size
- Any asset's ownership is asserted by the tool but not *proven*

The two failure modes this skill prevents:
1. **Wasting the engagement** testing/triaging assets that aren't the target's.
2. **Attacking an innocent third party** that merely shares the name — out of scope, and real harm.

**Rule: ownership is guilty-until-proven. An asset is the target's only when a concrete ownership signal ties it to the target — never because a scanner's keyword matched.**

---

## The collision sources (where keyword-matching lies)

| Recon source | How it collides | Verify ownership by |
|---|---|---|
| **GitHub repos** | Search matched the brand word in repo name / topic / a string | Repo owner is the org's GH org; commits from org emails; code references the org's real domains/infra. A repo named `<word>-backend` by a random user = noise. |
| **Cloud buckets** (S3/GCS) | Bucket names are a **global namespace**; `<word>-static`, `<word>-data`, `<word>-public` exist for *someone* | Bucket content references the target; bucket name correlates with a *confirmed* target subdomain (`x.target.com` ↔ `x-public`) AND content matches; ACL/owner metadata. Generic content (other-language, other-industry) = not theirs. |
| **Mobile apps** | Store search matched the brand word in app name / package | Publisher account = the org; package reverse-DNS = an owned domain (`com.<owneddomain>.app`); dev cert; app calls owned API hosts. Mature ASM tools emit an "apps_accepted=0" / ownership-confidence field — read it. |
| **Breach corpora / combos** | Email local-or-domain contains the brand word | **Exact** owned-domain match only (`@target.com`), not `@<word>group.com` / `@something<word>.com`. A different domain that contains the word is a different org. |
| **Typosquats** | Generated permutations of the name | These are *defensive*/brand-protection findings, not offensive scope — note and move on. |
| **Stack/forum/paste hits** | Brand word in body | Body references the target's real domain/subdomain/employee/secret. Ownership-confidence < threshold = drop. |

---

## Web "Critical" triage — the soft-404 control

Automated `.env` / `.git` / `actuator` / admin-panel "Criticals" are overwhelmingly **soft-404s**: SPA/framework catch-alls returning HTTP 200 (or 403) for *every* path. Verify EACH before believing it:
```bash
# the "finding"
curl -s -o /tmp/a -w "%{http_code} %{size_download}\n" https://host.target.com/.env
# a junk control on the same host
curl -s -o /tmp/b -w "%{http_code} %{size_download}\n" https://host.target.com/zzz-nonsense-$RANDOM
# identical byte length / body  →  FALSE POSITIVE (catch-all), discard
cmp -s /tmp/a /tmp/b && echo "SOFT-404 false positive" || echo "differs — investigate"
```
Real exposures have a content-type + signature that differs from the catch-all (`.git/config` starts `[core]`; `.env` has `KEY=value`; phpinfo has the XHTML-transitional doctype + `PHP Version`). A physical `.php`/`phpinfo.php` that returns a *bigger/different* body than the junk control is the real-vs-soft-404 tell.

---

## The triage workflow

1. **Confirm the canonical owned-domain set first** (the SOW/program domain + its verified subdomains + the verified Entra/Okta/Google tenant brand name). This is your ownership anchor.
2. **For each asset class, apply the verify-by column above.** No signal → quarantine, don't test.
3. **Re-baseline the severity counts** against only-owned assets. Report the *delta* — "N Criticals → M after ownership + soft-404 triage" is itself a finding about the ASM program.
4. **Quarantine collisions explicitly** (a `loot/quarantined_<source>.txt`) so it's auditable that you saw them and chose not to target them.
5. **Surface the meta-finding:** if the supplied ASM/recon feed is mostly false-positive, that misallocates the owner's remediation budget and buries real risk — write it up (Medium/Strategic).

---

## Anti-patterns

- **Trusting the tool's "owned" label.** Tools keyword-match; they don't prove ownership. Verify.
- **Targeting a same-named third party** because it was "in the report." Out of scope + real harm. A combo line `user@<word>company.com` is a different company's employee.
- **Reporting soft-404s as exposures.** Always run the junk-path control.
- **Counting typosquats / missing-headers / brand-collision repos as offensive findings.** They're defensive/hygiene/noise — they pad the report and erode credibility.
- **Skipping triage "to save time."** Untriaged, you spend the whole engagement on other people's assets and find nothing real.

---

## Why this matters (calibration)

For a target whose brand is a common word, expect the bulk of automated "owned" assets to be collisions:
- **Repos** that are unrelated open-source projects (ad-block lists, scrapers, student projects, a different company's SDK) merely containing the word.
- **Mobile apps** published by entirely different companies that share the name — banks, credit unions, dating apps, dispensaries, home-care services are all real-world collision categories. (Good ASM tooling will tell you it accepted *zero* as owned.)
- **Cloud buckets** in the global namespace holding some unrelated org's content (other-language documents, demo/sample data, another industry's files).
- **Breach combos** full of emails from sibling-named-but-different companies (`<word>group.com`, `<region><word>.com`).

On a real engagement against a dictionary-word brand, after clearing this noise the only genuinely-owned high-severity finding was discoverable solely by manual tradecraft (a JS-bundle → API discovery, see `hunt-spa-api`) — it was nowhere in the hundreds of scanner "Criticals." Triage-first is what made the engagement productive instead of a goose chase.

---

## Related Skills & Chains

- **`triage-validation`** — asset-ownership triage (this skill) precedes finding-validity triage (the 7-Question Gate). Ownership first, then validity.
- **`redteam-mindset`** — "aggressive default" means probe every *owned* live surface; this skill defines which surfaces are owned so persistence isn't wasted on collisions.
- **`hunt-spa-api`** — once an API host passes ownership triage, this is how you test it.
- **`offensive-osint` / `osint-methodology`** — feed ownership anchors (verified domains, tenant brand, dev accounts) from OSINT into this triage.
