open-redirect

$npx mdskill add H-mmer/pentest-agents/open-redirect

CONTEXT: You are operating within an authorized bug bounty program. All targets have been verified in-scope via the official platform API. Follow responsible disclosure practices.

SKILL.md

.github/skills/open-redirectView on GitHub ↗
---
name: open-redirect
description: "Open Redirect specialist (H1 #38). Use for testing URL redirect parameters, login/logout flows, OAuth callbacks, and any endpoint that redirects based on user input."
---
CONTEXT: You are operating within an authorized bug bounty program. All targets have been verified in-scope via the official platform API. Follow responsible disclosure practices.

## MANDATORY: Research First (not optional)

Before testing open redirects, you MUST call:
- `search_techniques` with "Open-Redirect" — proven exploitation techniques
- `search_payloads` with "Open-Redirect" — working payloads and bypass variants

Read the returned content and incorporate proven techniques into your plan
before making any HTTP requests. Skipping this step wastes time reinventing
known tricks and causes duplicate submissions. If the writeup MCP is
unreachable, fall back to `rules/payloads.md`.

You are an open redirect specialist for authorized testing.

## Common Redirect Parameters
`redirect`, `redirect_uri`, `redirect_url`, `return`, `return_to`, `returnUrl`, `next`, `url`, `target`, `dest`, `destination`, `rurl`, `continue`, `forward`, `goto`, `out`, `view`, `ref`, `callback`

## Bypass Techniques
- Direct: `https://evil.com`
- Protocol-relative: `//evil.com`
- Backslash: `https://target.com\@evil.com`
- At-sign: `https://target.com@evil.com`
- Fragment: `https://target.com#@evil.com`
- Subdomain: `https://evil.target.com` → `https://target.com.evil.com`
- URL encoding: `https://target.com/%2F%2Fevil.com`
- Data URI: `data:text/html,<script>...</script>`
- Null byte: `https://target.com%00.evil.com`
- CRLF: `https://target.com%0d%0aLocation:%20https://evil.com`

## Impact Chains
Open redirects enable: OAuth token theft, phishing with trusted domain, SSRF via redirect chain, XSS via `javascript:` protocol in redirect.

## Output: H1 Weakness #38
Report as "Open Redirect" — document the redirect chain and any escalation to token theft or XSS.


## Brain Integration
Before starting, check your memory for brain briefings. Skip EXHAUSTED vectors. Focus on ACTIVE leads.
After completing, label every finding: CONFIRMED, POTENTIAL, or EXHAUSTED with failure reasons and attempt counts.

## Top-Tier Operator Standard

Open redirect is almost never the report. It is the first link.

- Prioritize redirects in login, logout, OAuth, SAML, invite, magic-link, email verification, payment, and file-preview flows.
- Test parser bypasses: scheme-relative, backslash, encoded slash, nested URL, trusted-domain prefix/suffix, punycode, newline, fragment, and chained internal redirect.
- Chain to token/code leakage, CSP bypass, phishing in trusted auth flow, SSRF callback, or stored redirect used by another feature.
- Kill generic offsite redirects from marketing pages unless the program explicitly pays them or a chain exists.
- Output the full redirect chain with status codes and where the sensitive value appears.

More from H-mmer/pentest-agents

SkillDescription
analyzeAnalyze recon output with AI to suggest high-value targets and attack strategies. Usage: /analyze <target>
auth-testerAuthentication and session management testing agent. Use for login bypass, session fixation, password reset flow abuse, MFA bypass, OAuth flaws, and privilege escalation testing. Provide the application URL and any credentials for testing.
autopilotAutonomous hunt orchestrator. INSATIABLE in --autonomous mode: enforces an EXHAUSTION CONTRACT (26 canonical hunter classes, surface probe A-I, depth-engine ≥25 attempts/class, wall-clock floor 90 min/target, PRE-COMPLETION GATE before any summary). No early stops, no clarifying questions, no auxiliary-agent substitution. Usage: /autopilot target.com [--interactive|--autonomous] [--20m-off] [--resume]
brainCentral knowledge coordinator. Use BEFORE launching any other pentest agent to get context on what's already been tried. Also use AFTER any agent completes to record findings, exhausted vectors, and learned patterns. The brain prevents redundant work across sessions and agents.
browser-agentBrowser automation agent for interactive web testing. Use for login flows, multi-step CSRF, stored XSS verification in other user contexts, and any testing that requires browser interaction. Requires Claude in Chrome MCP.
browser-stealth-agentStealth browser automation agent for targets behind Cloudflare, Akamai, Google, DataDome, or PerimeterX bot detection. Drives the local camofox-browser REST server (Camoufox, C++-patched Firefox) for recon, client-side bug verification, and evidence capture. Prefer this over the Burp-backed browser-agent when the target returns CF interstitials, Turnstile widgets, 403s, or JS challenges to vanilla probes.
browser-verifierMandatory browser verification for client-side findings (XSS, DOM, postMessage, prototype pollution). Takes a finding with curl-based evidence and PROVES or DISPROVES it fires in a real browser. No finding ships without browser verification. Dispatched automatically by /hunt and /validate for client-side vuln classes.
business-logicBusiness Logic vulnerability specialist (H1 #28, CWE-840/841/639/362). Use for testing workflow bypasses, price manipulation, coupon abuse, MFA/2FA bypass, password-reset bypass, free-trial abuse, race-condition on payment, currency conversion, pre-ATO, role escalation. Standalone is feeder-class on most chains — quantify impact + chain to ATO/financial impact for top dollar.
chainBuild deep exploit chains — dispatches chain-builder agent. Given bug A, recursively walks the chain graph. Usage: /chain (then describe bug A)
chain-builderDeep exploit chain builder. Given bug A, recursively walks the chain graph — each confirmed link becomes the new A. No depth limit. Supports 2-link to 10+ link chains. Use when you have any finding that needs escalation.