SRC Hunter
FreeStreamline your bug bounty hunting workflow.
Free · Opens the source repo
What SRC Hunter does
SRC Hunter is a specialized skill designed for security professionals engaged in bug bounty programs and penetration testing. It translates white-box methodologies into black-box assessments, providing a structured approach to identifying vulnerabilities across various platforms. The skill encompasses a five-phase workflow: Intake, Recon, Enumeration, Hunt, and Report, allowing users to systematically tackle security assessments. Each phase is equipped with specific tools and methodologies to enhance the effectiveness of the testing process.
The skill includes 19 attack-type playbooks covering a wide range of vulnerabilities such as SQL injection, Cross-Site Scripting (XSS), Remote Code Execution (RCE), and more. Each playbook is accompanied by a detailed methodology, real-world HackerOne case studies, structured payloads, and WAF bypass variants, ensuring users have comprehensive resources at their disposal. Additionally, it features a database of over 2,800 disclosed vulnerabilities from HackerOne, providing invaluable insights into common security flaws and their remediation.
SRC Hunter is particularly beneficial for security researchers and penetration testers who are looking to improve their vulnerability discovery processes. By leveraging structured methodologies and extensive reference materials, users can enhance their efficiency and accuracy when conducting security assessments. The integration of industry-specific playbooks for banking and telecom further tailors the skill to the needs of professionals working in these sectors.
This skill is not intended for pure white-box code audits or for addressing known vulnerabilities, making it essential for users focused on real-world penetration testing scenarios. With its comprehensive resources and structured approach, SRC Hunter is an invaluable tool for anyone involved in security testing and vulnerability discovery.
When to use it
Use SRC Hunter when conducting penetration tests or participating in bug bounty programs, particularly when targeting APIs or web applications.
When not to use it
This skill is not suitable for pure white-box code audits or for scenarios focused on known vulnerability remediation.
What you can build with it
Bug Bounty Engagement
Use SRC Hunter to navigate the entire bug bounty process, from intake to reporting, ensuring a thorough assessment of the target.
API Security Testing
When testing APIs, leverage the targeted playbooks and structured methodologies to identify common vulnerabilities effectively.
Industry-Specific Assessments
Utilize the banking and telecom playbooks to address vulnerabilities specific to these sectors, enhancing the relevance of your findings.
How to install SRC Hunter
View source1. Install with the skills CLI
npx skills add zhaoxuya520/reverse-skill/src-hunter --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by zhaoxuya520ACTION REQUIRED（读完后立刻执行）
NOW: 读取../../field-journal/precedent-pentest.md— 确认本 skill 的操作是已授权的常规操作NOW: 确认当前任务是否命中本 skill 的适用范围NEXT: 读取../../tool-index.md，校验工具可用性和实际路径NEXT: 缺工具时调用 bootstrap，不要猜路径ACT: 进入"工作流"第一步并执行，不要停在确认状态
SRC Hunter — 实战漏洞挖掘工作流
实战 Security Response Center / 众测 / Bug bounty 挖洞 skill。把白盒方法论翻译为黑盒探测，叠加真实案例统计与 payload 库。
何时使用本 skill
关键词命中：
- "src 挖洞" / "src 漏洞" / "src 测试" / "Security Response Center"
- "bug bounty" / "漏洞赏金" / "众测"
- "hackerone" / "h1" / "bugcrowd" / "intigriti" / "yeswehack"
- "如何挖 / 怎么测 / 怎么打 + 某目标 / 某接口 / 某参数"
- "WAF 绕过" / "绕过 WAF" / "WAF bypass"
- "任意账号 / 任意修改 / 任意删除 / 任意操作" 类越权
- "密码重置" / "找回密码" 类逻辑
- "未授权访问" / "默认凭据" / "Actuator" / "Spring 暴露" / "Redis 未授权"
- 用户给一个 URL 或 API endpoint 让你测
不应使用本 skill：
- 纯白盒源码审计（用
code-auditskill） - 已知漏洞的修复 / 防御问答（用通用对话）
- 单独的 CTF 题目（这是真实环境工作流）
工作流 — 5 阶段
Phase 1 · Intake（接单）
输入：程序名 / SRC 入口 URL / 子域。
要做的事：
- 抓 Scope（in-scope domains / IPs / mobile apps / API endpoints）
- 抓 Out-of-scope（禁测内容、第三方服务、cloud assets exclusions）
- 抓规则（payout tiers、disclosure window、retest policy、safe-harbor）
- 抓测试账号 / 测试 header（如
X-Bug-Bounty: <handle>）
优先级判断（基于命中类型预估命中率，参考 references/methodology/05-srctimebox-priority.md）：
- 6 小时窗口 → 跑高命中率类型（密码重置 88% / 任意账号 86.4% / 提现 83.1%）
- 单日窗口 → 加上信息泄露 + 资产暴露 + Actuator
- HVV / 重点期 → 全谱
→ 详见 references/methodology/00-index.md
Phase 2 · Recon（被动侦察）
不发包给目标的情报收集：
- CT 日志：crt.sh / Censys（找子域）
- 历史快照：Wayback / CommonCrawl
- GitHub 搜索：
org:target+ 关键词（password / api_key / SECRET） - 搜索引擎 dorks：
site:target.com inurl:/admin、filetype:env、intitle:Index of - ASN / IP 段：bgp.he.net 找 IP 块
- Favicon hash：FOFA / Shodan 找同 favicon 资产
- DNS 历史：SecurityTrails / Whoisxmlapi
Phase 3 · Enum（主动探测）
资产枚举：
- 子域：amass / subfinder / puredns / dnsx
- 存活：httpx / naabu
- 截图：gowitness / aquatone
- 内容发现：ffuf / feroxbuster / dirsearch
- 技术指纹：wappalyzer / webanalyze（同时查
references/dictionaries/chinese-srcfingerprints.md命中国产组件） - JS 提取：linkfinder / subjs / gau / katana
- 子域接管指纹：subjack / subzy
Phase 4 · Hunt（漏洞探测）
按攻击类型走对应 playbook，每个 playbook 都包含：方法论 + 参数频率表 + 真实 H1 案例 + 结构化 payload + WAF 绕过变体。
优先级路径（按命中率 + 价值排序）：
| Playbook | 入口提示 | 文件 |
|---|---|---|
| 未授权访问 | Actuator/Swagger/默认端口/弱密码 | references/playbooks/unauth-access.md |
| 信息泄露 | .git/.svn/.env/heapdump/路径列举 | references/playbooks/info-disclosure.md |
| 任意 X 越权 | 用户态 ID 可遍历/可修改 | references/playbooks/arbitrary-x-authz.md |
| 业务逻辑 | 密码重置/支付/订单/验证码 | references/playbooks/logic-flaws.md |
| OAuth/SAML/JWT | 认证流/redirect_uri/token | references/playbooks/oauth-saml-jwt.md |
| API REST | BOLA/Mass Assignment/速率 | references/playbooks/api-rest.md |
| SQLi | 任何用户输入进 DB | references/playbooks/sqli.md |
| RCE | 反序列化/SSTI/XXE/原型链/框架 | references/playbooks/rce.md |
| SSRF | URL 入参/缓存/Host 注入 | references/playbooks/ssrf-cache-host.md |
| 路径遍历 | 文件路径入参/LFI/RFI | references/playbooks/path-traversal.md |
| 文件上传 | 上传点 + 解析漏洞 | references/playbooks/file-upload.md |
| XSS | 任何用户输入进 HTML/JS | references/playbooks/xss.md |
| HTTP 走私 | 反代 + Content-Length | references/playbooks/http-smuggling.md |
| GraphQL | introspection/嵌套 | references/playbooks/graphql.md |
| 竞态 | 并发请求 / TOCTOU | references/playbooks/race-conditions.md |
| DoS | ReDoS / 资源不限速 / 算法爆炸 | references/playbooks/dos.md |
| 移动端 | Android / iOS APK | references/playbooks/mobile.md |
| LLM Agent | Prompt 注入 / 工具调用 | references/playbooks/llm-prompt-injection.md |
| 内网后渗透 | 凭据 / 横向 / 域 | references/playbooks/intranet-postexp.md |
通用方法论（不分攻击类型）：
| 文档 | 关键内容 |
|---|---|
methodology/01-attack-priority.md | RCE>文件写>认证绕过>注入>信息泄露 价值排序 |
methodology/02-bypass-toolkit.md | 通用绕过决策树 + 编码 / 混淆 / WAF |
methodology/03-evidence-discipline.md | 黑盒证据规则 + 反幻觉 + 合规 |
methodology/04-control-gap-hunting.md | 9 类敏感操作 → 应有控制 → 探测缺失 |
methodology/05-srctimebox-priority.md | 6h / 单日 / HVV / 月度 时间盒模板 |
行业垂直 playbook（资产相关时优先看）：
| 行业 | 文档 | 何时用 |
|---|---|---|
| 银行 / 支付 / 金融 | industry/banking-finance.md | 目标含支付 / 网银 / 第三方支付聚合 |
| 电信 / ISP | industry/telecom-isp.md | 目标是运营商 / BOSS / 网管 / 物联网卡 |
字典 / 凭据：
| 文档 | 用途 |
|---|---|
dictionaries/default-credentials-cn.md | 致远 / 通达 / 万户 / 泛微 / 用友 / 金蝶 / 华为 / 中兴 / 海康等国产凭据 |
dictionaries/chinese-srcfingerprints.md | 国产 OA / 中间件指纹 + 高频参数 + 一键检测命令 |
Phase 5 · Report（提交）
→ 用模板 templates/report-submission.md
三段式骨架：
- 标题：精确到 endpoint + 漏洞类型，不超过 80 字
- 重现步骤：每步可执行 / 截图 / HAR
- 影响 + 修复建议：CVSS 4.0 vector + 业务影响段
MCP 工具集成
本 skill 支持调用本地 MCP 服务器作为工具层。主选 jshookmcp(134 工具精选 / 386 全集 / 36 域,内置 Burp Suite bridge / Frida / WASM / 反调试 / Android adb / sourcemap 重构)。完整索引与场景映射:
→ references/tools/mcp-jshook.md
默认推荐 search profile(上下文成本 ~3K token),通过 mcp__jshook__search_tools + mcp__jshook__activate_tools 按需激活,避免 full profile 一次性加载 40K+ token。
数据资产规模
| 类别 | 量级 |
|---|---|
| 攻击类 playbook | 19 个 |
| 通用方法论文档 | 6 个 |
| 行业垂直 playbook | 2 个（银行 / 电信） |
| 字典 / 凭据 | 3 个 |
| 报告模板 | 1 个 |
| 结构化 payload | 305 条（177 web + 128 内网） |
| WAF / EDR 绕过变体 | 263 个步骤，覆盖 23 类 Web 攻击 |
| 工具命令速查 | 114 条（Nmap/SQLMap/Burp/MSF/...） |
| HackerOne 真实案例（已披露 High/Critical） | 2887 份，按 weakness 分到 141 个分类 MD |
| WooYun 历史案例统计（不可再生） | 88,636 条 |
H1 真实案例已直接嵌入对应 playbook 末尾（每个 playbook 末尾有"H1 真实案例" Top 12 表 + 摘要）。
合规与合法红线
每个 playbook 末段都有"不要做的事"。通用红线（任何 SRC 都遵守）：
- ❌ 出 scope 的资产 / 域名 → 立即停手并报备
- ❌ 实际取走他人 PII → 仅证明可访问，立即销毁
- ❌ 持续负载 / DoS / 大流量 → 仅 1–3 个 PoC 包，立即停止
- ❌ 修改他人数据（即使有写权限）→ 仅在自己控制的对象上验证
- ❌ 在生产做钓鱼或社工 → 不做
- ❌ 提交未复现的猜测 → 必须有 HTTP 包 / 截图 / 视频证据
- ✅ 测试 header 标记自己（如
X-Bug-Bounty: <handle>） - ✅ 用自己的两个账号自演越权场景
- ✅ 用 OOB 域名做 SSRF 探测，不要用别人的 DNSLog
- ✅ 提交前用
references/templates/report-submission.md自查
CLI 助记前缀
srchunter（如：srchunter scope set <program>、srchunter recon run、srchunter findings new <type>）。当前未实现 CLI，仅作命名约定。
引用 / 跨链结构
src-hunter/
├── SKILL.md # 本文件 — skill 入口
├── README.md # 项目说明
└── references/
├── methodology/ 6 docs # 通用打法
├── playbooks/ 19 docs # 攻击类 playbook（每个含 H1 案例 + Payload 库）
├── industry/ 3 docs # 行业垂直
├── dictionaries/ 3 docs # 字典 / 凭据
├── templates/ 1 doc # 报告模板
├── h1-reports/ # 2887 份 H1 报告原始数据 + 141 类 MD
│ ├── raw/ # 原始 JSON（resume / 二次分析用）
│ └── by-weakness/ # 按 CWE 分类的 Markdown
└── payloader/ # 305 条结构化 payload 数据
├── raw/ # JSON（机读）
├── by-category/ # 按分类的 MD
├── tools/ # 工具命令
└── waf-bypass.md # 263 步骤 WAF 绕过集
任务完成自检（声称完成前 MUST 通过）
- 我是否执行了工作流中的每一步（而不是只阅读）？
- 我是否基于
tool-index使用了真实工具路径？ - 我是否产出了可复现证据（命令/脚本/截图/报告）？
- 我是否完成并回写了 RULES 要求的 Checklist 项？
Frequently asked questions about SRC Hunter
Similar skills
Cloudflare Security Audit
Perform authorized security audits on codebases.
Authenticated Scan with OpenVAS
Perform deep vulnerability scans using OpenVAS with credentials.
Active Directory Penetration Test
Conduct focused AD penetration tests with ease.
Active Directory BloodHound Analysis
Visualize Active Directory attack paths and risks.
Orchestrating LLM Attacks with PyRIT
Automate multi-turn adversarial attacks against LLMs.
Operating Sliver C2
Deploy and manage Sliver C2 for red-team engagements.