tradecraft-attack-scenarios
Turn a goal + a scope into a concrete, ordered attack scenario across multiple skills — not one technique in isolation. Load at the START of an engagement, on "where do I even begin", when a target has many surfaces, or to plan an objective-driven path (e.g. "reach domain admin", "prove data exfil")
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-attack-scenariosGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote94cb7fd0…e0bc057e
94cb7fd0c49f…6737e0bc057e1 arquivo · 1.6 KBVarreduraBaixonenhum achado
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-attack-scenarios@ee0e0c5
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When it applies
You have an authorized scope and an objective, and the target exposes several possible surfaces. Before running anything, you need a plan that sequences the right skills toward the objective and adapts as evidence comes in. This is the layer above individual techniques.
Why it works
Real engagements are graphs, not checklists: each result changes what's worth trying next. Planning
the scenario explicitly — objective, hypotheses, ordered leads, decision points — is what turns a
pile of 127 techniques into a coherent path, and it's exactly what the secskills watch Attack Map
renders (lead, status, rationale).
Method
- State the objective in impact terms: "read another tenant's data", "code exec on the app host", "domain admin". Everything is prioritised by what moves you toward it.
- Enumerate surfaces from recon (
recon-*): web, API, cloud, AD, network, people. Each surface is a branch. - Generate leads per surface and score each by impact × likelihood × cost/noise. A likely high-impact, low-noise lead goes first.
- Order into a scenario: recon → highest-value lead → the pivots each success unlocks. Write it
to
plan.mdas an ordered, checkbox strategy; tag each lead with a slug for the activity log. - Define decision points: for each lead, note "if confirmed → pivot to X; if blocked → why, and
the fallback". This is the branching that makes it adaptive (see
tradecraft-pivot-decisions). - Re-plan on evidence: every confirmed finding or dead end updates scores and can reorder what's next. The plan is living, not a one-shot.
Gotchas
- Don't breadth-scan everything — depth on the highest-value lead beats shallow coverage.
- Objective drift: if a lead doesn't advance the stated objective, park it, don't chase it.
- Keep it inside scope; an attractive lead outside
scope.txtis not a lead (loadtradecraft-scope-roe).
Verify success
There is a written plan.md with an objective, ordered leads carrying rationale, and explicit
"if/then" pivots — and the agent is working the top lead, not wandering.
References
MITRE ATT&CK (tactic ordering); PTES; the exploit-chaining and tradecraft-pivot-decisions skills.
Arquivos desta versão
- SKILL.md2.8 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Não | Não |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Nã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ão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 de nov. de 2026 | ee0e0c5 | 94cb7fd0 | Assinada | – |
Mais de NoorQureshi
Tudo deste publicadorMais em Web e bug bounty
Ver a categoria- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
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/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login