SuperAPI AI Directory

attack-chain

General & other

View repository

Updated 10-16 08:47

About this skill

⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited.

Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:

  1. Ask the user to state the exact target URL, IP, account, or resource.
  2. Ask the user to confirm written authorization and the permitted scope.
  3. Show the exact command(s) and explain their expected effect.
  4. Wait for explicit confirmation in the current conversation.

Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.

Attack Chain Orchestration Skill

When to Use

  • An authorized engagement spans multiple kill-chain phases.
  • Coordinating several specialist skills into one coherent attack path.

When to route to this Skill

In the following scenariosmustfirst go through this Skill for full-chain planning, then dispatch to specific sub-Skills for execution:

Scenario Why orchestration is needed
"Help me do a complete penetration test" Needs planning for the entire process from information gathering to reporting
"From the external network to the domain controller" Spans multiple stages: boundary breach → privilege escalation → lateral movement → AD
"HW attack-defense exercise" Needs a complete attack chain + stealth + trace cleanup
"Assess this target's attack surface" Needs multi-dimensional information gathering + path planning
"I got a webshell, what should I do next" Needs to plan the follow-up path from the current foothold
"Help me plan the attack path" Clearly needs path orchestration
"How far can I get from this vulnerability" Needs to assess the vulnerability's chained exploitation value
"Bug Bounty continuous monitoring" Needs an automated multi-stage process
"Full internal network penetration process" Combination of lateral movement + privilege escalation + domain attacks
"Proximity penetration plan" Combination of physical access + internal network penetration
"Supply chain attack path" Cross-organization multi-hop attack
"Phishing + post-exploitation" Combination of initial access + subsequent exploitation

Single-stage tasks do not need to go through this Skill:

  • Only doing port scanning → go directly to pentest-tools/
  • Only doing SQL injection → go directly to pentest-tools/
  • Only doing APK reverse engineering → go directly to apk-reverse/
  • Only doing domain penetration → go directly to windows-ad/SKILL.md

Orchestration principles

The role of this Skill

用户提出多阶段任务
    ↓
attack-chain/SKILL.md(本文件)
    ↓ 规划攻击路径、确定阶段顺序
    ↓ 评估每阶段所需工具和方法
    ↓
分发到具体子 Skill 执行:
    ├── pentest-tools/     → 工具调用、漏洞利用
    ├── apk-reverse/       → 移动端渗透
    ├── js-reverse/        → Web 前端突破
    ├── reverse-engineering/ → 二进制分析
    ├── ida-reverse/       → 深度逆向
    └── browser-automation/ → 自动化操作
    ↓
每阶段完成后回到本 Skill 评估下一步
    ↓
全部完成 → docs-generator 生成报告

Path planning decision tree

拿到目标后:
1. 目标是什么?(Web/内网/云/移动/IoT)
2. 当前有什么?(外部视角/已有凭据/已有据点)
3. 最终目标是什么?(域控/数据/特定系统/证明影响)
4. 约束条件?(时间/隐蔽性/不可触碰的系统)
    ↓
根据以上信息规划最短路径
    ↓
一条路走不通 → 回到本 Skill 重新规划备选路径

Complete attack chain stages


For detailed phase methodology, toolchains, and playbooks, refer to:

Iron rules of red team operations

Three bottom lines

  1. All operations must obtain written authorization
  2. Data exfiltration must be anonymized
  3. Clean up all attack traces (including memory residency)

Operational discipline

  • Assess the risk level before each operation (low/medium/high/critical)
  • Notify the project manager before high-risk operations
  • Maintain operation logs (time, action, result)
  • Report high-risk vulnerabilities immediately upon discovery; do not expand exploitation
  • Do not affect business availability (DoS is prohibited)
  • Do not access/download real user data

Typical failure cases

Cause of failure Consequence Lesson
Mimikatz memory dump not cleared Blue team traces the complete attack path Clean up immediately after operations
C2 domain flagged by threat intelligence Blocked on the first connection Use newly registered domains + domain fronting
Phishing email triggers DLP alert Blue team issues an early warning Test email gateway rules
Lateral movement triggers a honeypot Exposes attack intent Identify honeypots before acting

Tool quick reference

Information gathering

subfinder amass httpx naabu katana gau dnsx nmap whatweb wpscan

Vulnerability Exploitation

nuclei sqlmap sstimap xsstrike burpsuite metasploit

Privilege Escalation

winPEAS linpeas GodPotato PrintSpoofer watson

Lateral Movement

mimikatz crackmapexec/netexec impacket bloodhound certipy coercer responder evil-winrm

C2 Framework

cobalt-strike sliver havoc mythic adaptixc2

Close Access Penetration

fluxion aircrack-ng proxmark3 rubber-ducky wifi-pineapple


Relationship with Other Skills in This Package

Requirements Route to
Deep Web Vulnerability Exploitation pentest-tools/SKILL.md
Detailed Steps for Internal Network AD Attacks windows-ad/SKILL.md
Reverse Engineering Malware Samples reverse-engineering/SKILL.md
APK Reverse Engineering (Mobile Penetration) apk-reverse/SKILL.md
JS Frontend Signature Bypass js-reverse/SKILL.md
Automated Mass Penetration Pentest Swarm AI(pentestswarm scan --swarm)
AI-Assisted Penetration mcp-kali-server / metasploitmcp / hexstrike-ai
Report Generation docs-generator/SKILL.md
Attack Path Diagram diagram-generator/SKILL.md

Task Completion Self-Check (MUST pass before claiming completion)

  • Did I execute each step in the workflow (rather than just reading)?
  • Did I base it on tool-index using real tool paths?
  • Did I produce reproducible evidence (commands/scripts/screenshots/reports)?
  • Did I complete and write back the Checklist items required by RULES?

Limitations

  • Execution of attack stages requires written authorization per target.
  • Assumes supporting tooling (recon/exploit kits) is installed and licensed where applicable.

Adapted from zhaoxuya520/reverse-skill (MIT).