Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
noorqureshi/tradecraft-complex-engagementsWeb e bug bounty

tradecraft-complex-engagements

⁨Structure and discipline for complex, multi-stage targets — where the path is a chain of several bugs across multiple hosts, needs source review / custom exploit work, and spans sessions. Load when a foothold needs chaining, work spans multiple hosts, you're deep in dead-ends, or "stuck", "chain", "⁩

v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tradecraft-complex-engagements

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
hlaSyyi+L3…wMtxDuCQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote7621400e…ee49a05f
7621400e90b1…5665ee49a05f1 arquivo · ⁦1.9 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-complex-engagements@ee0e0c5

Este item ainda não foi escrito no seu idioma, então aparece em English.

Hard targets differ in kind, not just difficulty. The path is usually a chain of 2–4 bugs wrapped in deliberate dead-ends — sometimes needing source review, custom exploit work, reversing, or a crypto attack — and it often spans multiple hosts and sessions. Wins come from disciplined enumeration and ruthless dead-end tracking, not a bigger exploit. In-scope, authorized targets only (see tradecraft-scope-roe).

Keep a working record (per engagement)

text
engagement/
  state.md          # live status + a "haven't tried yet" list
  deadends.md       # ruled-out leads WITH the reason each was dropped   ← the key habit
  chains/           # working exploit chains / PoC drafts, one link at a time
  findings/         # confirmed findings + evidence
  hosts/<host>/     # one subdir per internal host reached

Extended method

  1. Exhaustive recon. Every port, vhost, parameter, version string. The lead is often in the thing you skipped (recon-arsenal, recon-content-discovery).
  2. Clue harvesting. Log everything, including what looks irrelevant — odd headers, unusual filenames, custom apps, strange responses.
  3. Foothold by chain. Expect to combine bugs (e.g. SSRF → internal service → deserialization → RCE). Build it in chains/, verifying each link before adding the next (exploit-chaining).
  4. Stabilize + situational awareness. Get a stable shell, then map users/services/internal network before moving.
  5. Pivot / lateral. Enumerate internal reachability; one hosts/<host>/ per host; repeat the loop per host (network-pivoting-tunneling).
  6. Privilege escalation (often custom). Standard checks first, but be ready for a target-specific vector — a custom SUID binary, a bespoke service, an ACL path (privesc-arsenal).
  7. Write up the chain. Document it end to end; each link needs reproduction steps and evidence (reporting-bug-bounty-writeup).

Dead-end discipline (the skill that separates good operators)

  • The moment a lead dies, write it in deadends.md with why it's ruled out. This stops you re-walking dead-ends over a multi-day engagement and reveals what you actually haven't tried.
  • Keep a live "haven't tried yet" list in state.md. When stuck, work that list before reaching for exotic exploits.
  • Truly stuck? Re-run enumeration on the least-examined service, diff against earlier output, and re-read the clue log. The path is usually already in your notes.

Custom-exploit workflow

Read any public PoC fully before running it and note the source (exploit-poc-development). When a PoC needs adapting, keep a clear record of what changed and why — that becomes report content and a capture-worthy new skill. Review application source when you have it: auth logic, input handling, serialization, crypto (code-review-methodology).

Capture what you learn

When an engagement teaches a reusable technique (a novel chain, a bespoke privesc, a crypto attack), add it as a new stability: learning technique skill under the right domain so future work benefits (see the library README.md).

Working style: enumerate first, track dead-ends, build chains incrementally, and explain your reasoning — on complex targets the reasoning is the skill.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.10.14-ee0e0c513 de nov. de 2026ee0e0c57621400eAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login