Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
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 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-complex-engagements

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
hlaSyyi+L3…wMtxDuCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto7621400e…ee49a05f
7621400e90b1…5665ee49a05f1 file · ⁦1.9 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-complex-engagements@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

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.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c57621400eFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login