by 详细分析 ▾
运行时依赖
版本
HexStrike 1.0.0 — Initial release - Launches a cybersecurity assistant for CTF, pentesting, recon, binary analysis, forensics, cloud security, and more. - Enables direct CLI access to 150+ security tools with methodology-driven workflows and no middleware. - Provides structured guidance for CTF challenges, including category identification and tool usage methodologies. - Includes phased reconnaissance and penetration testing workflow, with tool usage and output management advice. - Offers quick syntax lookup by referencing curated documentation for 80+ tools. - Emphasizes safety, authorization, and non-invasive best practices for tool execution.
安装命令 点击复制
技能文档
Overview
Execute security tools directly via exec. No middleware, no MCP server — direct CLI access to 150+ security tools with methodology-driven workflows.
First Step: Check Available Tools
Before starting any engagement, run the tool checker to see what's installed:
bash scripts/tool-check.sh # All categories
bash scripts/tool-check.sh network # Just network tools
bash scripts/tool-check.sh web # Just web tools
Adapt the workflow to available tools. If a preferred tool is missing, suggest installation or use alternatives.
CTF Workflow
When given a CTF challenge:
- Identify category from description/files (web, crypto, pwn, forensics, rev, misc, OSINT)
- Read
references/ctf-playbook.mdfor the matching category section - Triage — run quick identification commands before heavy tools
- Iterate — CTF is exploratory; try the obvious first, escalate to specialized tools
- Document findings as you go — note promising leads
Category Identification Hints
| Indicators | Category |
|---|---|
| URL, web app, login page, cookies | web |
| Ciphertext, hash, encoded data, RSA, AES | crypto |
| Binary file, ELF, PE, segfault, nc connection | pwn |
| Image file, pcap, memory dump, disk image | forensics |
| Binary to analyze, "what does this do", crackme | rev |
| Username, location, social media, domain | OSINT |
| Encoding, QR code, audio file, esoteric | misc |
Recon / Pentest Workflow
For reconnaissance or penetration testing engagements:
- Read
references/recon-methodology.mdfor the full phased approach - Phase 1: Passive recon (subdomains, DNS, WHOIS, certificate transparency)
- Phase 2: Active recon (port scanning, service enumeration)
- Phase 3: Vulnerability scanning (nuclei, nikto, nmap scripts)
- Phase 4: Web app testing (directory brute-force, injection testing)
- Phase 5: Credential attacks (only when authorized)
Tool Reference
For quick syntax lookup on any of the 80+ tools, read references/tool-reference.md.
Execution Guidelines
Output Handling
- Pipe long outputs to files:
nmap ... -oA /tmp/nmap_results - Use
| head -50or| tail -20for initial review - Save important results:
> /tmp/_ _results.txt
Safety
- Never run offensive tools against targets without explicit authorization
- Default to non-invasive scans first (passive recon, version detection)
- Escalate to active testing only when confirmed authorized
- Use
--batchflags where available to avoid interactive prompts (e.g., sqlmap) - Set reasonable timeouts and rate limits to avoid disruption
Tool Installation
If critical tools are missing, suggest install commands:- Debian/Ubuntu:
sudo apt install - pip tools:
pip3 install - Go tools:
go install@latest - Kali Linux: Most tools pre-installed;
sudo apt install kali-tools-*for categories
Long-Running Scans
Useexec with background: true and yieldMs for scans that take minutes:
exec: nmap -sV -sC -p- -oA /tmp/full_scan
background: true, yieldMs: 30000
process(action=poll).
免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制