oauth-attacks

Test OAuth 2.0 and OIDC implementations for authorization code interception and misconfigurations.

18|3|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/kalpmodi/akira --skill oauth-attacks-kalpmodi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oauth-attacks
Source: https://github.com/kalpmodi/akira/tree/main/skills/oauth-attacks
Command: npx skills add https://github.com/kalpmodi/akira --skill oauth-attacks-kalpmodi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This playbook helps security professionals identify and exploit OAuth 2.0 and OpenID Connect weaknesses, enabling reliable validation of authorization flows and configuration issues without relying on server-side logging.

Core Features & Use Cases

  • Phase 1 - OAuth Endpoint Discovery
  • Phase 2 - Redirect URI Bypass (Highest Impact)
  • Phase 3 - CSRF (Missing or Bypassable State Parameter)
  • Phase 4 - Token Leakage via Referer / postMessage
  • Phase 5 - PKCE Bypass & Code Interception
  • Phase 6 - JWT/Token Attacks on OAuth Tokens
  • Phase 7 - Token Leakage in Logs / Headers
  • Phase 8 - OAuth Account Takeover Chains

Quick Start

Use this skill to begin a targeted OAuth security assessment by specifying a <target> domain and an optional <focus>.

Frequently Asked Questions about oauth-attacks

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

FAQPage Schema
How do I test for OAuth 2.0 redirect_uri bypass vulnerabilities?

Testing OAuth 2.0 redirect_uri bypasses involves manipulating the redirect parameter in authorization requests to identify weak validation logic. This Skill automates endpoint discovery and bypass analysis to detect misconfigurations allowing code interception or malicious redirection.

What is the best way to check for PKCE bypass and CSRF state parameter issues in OIDC?

Checking PKCE bypass and CSRF state parameter issues requires verifying missing or bypassable state validation and code challenge logic. This Skill evaluates OIDC token flow integrity to detect missing CSRF protections and exposed authorization codes.

How does token leakage occur via Referer headers or postMessage in OAuth flows?

Token leakage occurs when authorization codes or access tokens are exposed through HTTP Referer headers or insecure cross-origin postMessage calls. This Skill analyzes redirect handling and token transmission paths to identify these specific data exposure vulnerabilities.

Can I use this for enterprise apps and bug bounty security audits?

Yes, you can use this Skill for enterprise apps and bug bounty security audits. It applies OAuth provider testing to redirect_uri handling, token flow integrity, and account takeover chains, generating clear evidence templates for reproducible findings.

How do I perform an OAuth account takeover chain analysis?

Performing OAuth account takeover chain analysis involves identifying linked vulnerabilities like token leakage and CSRF to hijack user sessions. This Skill guides end-to-end testing of authorization flows to map exploit chains and validate takeover scenarios.