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 установки+3 за 7 дней27 ЗвездыMITсинхронизировано 22 часа назад
Установка
Ещё нет NotHoly CLI? Сначала установите её.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-complex-engagementsПишет в ~/.notholy/skills после проверки подписи и SHA-256.
ПодписьПодписано, ed25519
Пакет7621400e…ee49a05f
7621400e90b1…5665ee49a05f1 файл · 1.9 KBПроверкаНизкийзамечаний нет
Источникgithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-complex-engagements@ee0e0c5
Эта запись еще не переведена на русский, поэтому показан текст на другом языке: 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)
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 reachedExtended method
- Exhaustive recon. Every port, vhost, parameter, version string. The lead is often in
the thing you skipped (
recon-arsenal,recon-content-discovery). - Clue harvesting. Log everything, including what looks irrelevant — odd headers, unusual filenames, custom apps, strange responses.
- 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). - Stabilize + situational awareness. Get a stable shell, then map users/services/internal network before moving.
- Pivot / lateral. Enumerate internal reachability; one
hosts/<host>/per host; repeat the loop per host (network-pivoting-tunneling). - 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). - 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.mdwith 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.
Файлы этой версии
- SKILL.md3.7 KB
Права
| Право | Заявлено | Найдено проверкой |
|---|---|---|
| Читает файлы | Нет | Нет |
| Пишет файлы | Нет | Нет |
| Выполняет команды shell | Нет | Нет |
| Ходит в сеть | Нет | Нет |
| Использует коннекторы | Нет | Нет |
| Управляет браузером | Нет | Нет |
Замечания проверки
Проверено 13 нояб. 2026 г.
Проверка не нашла в этой версии ничего подозрительного.
Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.
| Версия | Опубликована | Коммит | SHA-256 | Подпись | Изменение прав |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 нояб. 2026 г. | ee0e0c5 | 7621400e | Подписана | – |
Ещё от NoorQureshi
Всё от этого издателяЕще в категории «Веб и bug bounty»
Вся категория- 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
Спрашивайте обо всём, что позволяет ваш скоуп.
Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.
- 1/3
Создайте аккаунт
Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.
ЛичныйКомпания - 2/3
Пополните баланс
Картой. Оплата за токены, без подписки.
$5.00минимальное пополнение - 3/3
Спрашивайте
В чате, или установите CLI и выполните notholy login в терминале.
$ notholy login