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 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-attack-scenariosScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto94cb7fd0…e0bc057e
94cb7fd0c49f…6737e0bc057e1 file · 1.6 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-attack-scenarios@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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.
File di questa versione
- SKILL.md2.8 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 94cb7fd0 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Web e bug bounty
Vai alla 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login