sc-open-redirect

Detect open redirect vulnerabilities in web application redirect flows.

7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/fatihkan/badi --skill sc-open-redirect-fatihkan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-open-redirect
Source: https://github.com/fatihkan/badi/tree/main/.claude/skills/security-check/sc-open-redirect
Command: npx skills add https://github.com/fatihkan/badi --skill sc-open-redirect-fatihkan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open redirects occur when user-controlled input determines the destination of redirects, enabling phishing, OAuth token theft, and SSRF chaining. This skill helps identify and mitigate such flows in web applications.

Core Features & Use Cases

  • Detection of unvalidated redirects in web routes and redirect parameters.
  • Bypass Technique Coverage: protocol-relative URLs, backslash tricks, URL-encoding, data URIs, and javascript: schemes.
  • Remediation Guidance: generate actionable findings with allowlist validation suggestions for safe redirects.

Quick Start

Run a scan of your web routes to detect unvalidated redirect parameters and generate remediation guidance.

Frequently Asked Questions about sc-open-redirect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect open redirect vulnerabilities in my web application?

To detect open redirect vulnerabilities, scan your server-side web routes and client-facing pages for unvalidated URL parameters controlling redirect destinations, generating structured findings with remediation guidance.

What are common open redirect bypass techniques I need to check for?

Common open redirect bypass techniques include protocol-relative URLs, backslash tricks, URL-encoding, data URIs, and javascript: schemes that manipulate redirect parameters to evade basic validation filters.

How do I prevent phishing risks from unvalidated redirects in OAuth flows?

Prevent phishing risks in OAuth flows by scanning login and deep-linking scenarios for user-controlled redirect inputs, enforcing allowlist validation for safe destinations, and applying structured remediation guidance.

Can I scan for open redirects across Node.js, Python, and Java server-side code?

You can scan for open redirects across Node.js, Python, and Java server-side code by analyzing HTTP endpoints and redirect flows to identify vulnerable patterns in URL parameters across these environments.

What is the best way to fix an open redirect vulnerability in a web route?

The best way to fix an open redirect vulnerability is to implement allowlist validation for redirect destinations, ensuring only approved URLs are accepted while blocking dangerous schemes and user-controlled inputs.

Why do unvalidated redirect parameters lead to OAuth token theft?

Unvalidated redirect parameters lead to OAuth token theft because attackers can manipulate the destination URL to intercept authorization codes or tokens, chaining the open redirect with malicious external sites.