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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-attack-scenariosEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete94cb7fd0…e0bc057e
94cb7fd0c49f…6737e0bc057e1 archivo · 1.6 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-attack-scenarios@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta 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.
Archivos de esta versión
- SKILL.md2.8 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 94cb7fd0 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Web y bug bounty
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login