Menu
Reason about JWT trust boundaries and whether token control can become privilege escalation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Four-phase autonomous bug bounty orchestration. Phase 0 maps external assets with deterministic Python helpers, Phase 1 lets AI prioritize attack surfaces, Phase 2 gives AI autonomous attack control, and Phase 3 produces verifier-only reports.
Four-phase autonomous bug bounty workflow. Python handles deterministic collection and verifier support; AI owns prioritization, attack reasoning, and autonomous direction changes.
Report generation agent. Convert verifier-confirmed findings into a fixed evidence-based report without adding speculative impact.
Rank reconnaissance-derived attack surfaces and design evidence-driven tests without active exploitation.
Test ranked attack surfaces autonomously, preserve evidence, and turn new access into additional attack-chain hypotheses.
A compact routing skill for choosing vulnerability hypotheses; detailed payloads live in references, not here.
| name | jwt-attack |
| description | Reason about JWT trust boundaries and whether token control can become privilege escalation. |
| metadata | {"tags":"jwt,auth,token,privilege-escalation"} |
判断 JWT 是否能被伪造、篡改、替换或用于跨角色访问，并把成功结果回注到所有相关接口。
references/INDEX.md；候选资源：jwt-analysis.md