Guide enumeration and testing of OAuth authorization, callback, token, and mobile deep link surfaces.
npx skills add https://github.com/jellaharshith/SWIFT --skill hunt-oauth
Please help me install this Agent Skill. Skill: hunt-oauth Source: https://github.com/jellaharshith/SWIFT/tree/main/swift/skills/cbh/skills/hunt-oauth Command: npx skills add https://github.com/jellaharshith/SWIFT --skill hunt-oauth
It helps you systematically hunt OAuth vulnerabilities that can lead to OAuth-based account takeover, session theft, and authentication bypass.
redirect_uri, test state CSRF weaknesses, check nonce replay/verification, and verify token endpoint completeness for prerequisite auth steps.Use hunt-oauth to produce an OAuth hunting plan for a target domain by instructing the AI to test redirect URI validation, state binding, and callback token leakage while focusing on the app’s browser and mobile deep link handlers.
High-intent search queries and answers about installing and using this skill.
To test OAuth redirect_uri validation weaknesses, map the authorization and callback endpoints to identify weak validation, then validate if attacker-controlled destinations can intercept token or code exfiltration flows.
State CSRF in OAuth occurs when the state parameter is missing or unvalidated, allowing attackers to forge authorization requests and hijack victim sessions through forced callback authentication.
Hunting OAuth vulnerabilities across mobile deep links requires enumerating deep link handlers to detect paths that redirect OAuth flows into attacker-controlled destinations, verifying token and code exfiltration risks.
Checking for nonce replay and referrer leakage in OIDC flows involves testing callback pages for header leakage and verifying if the token endpoint fails to reject reused nonce values during authentication.
Yes, this OAuth hunting methodology applies to prerequisite-auth bypass by verifying token endpoint completeness and checking if required authentication steps can be skipped during the token exchange process.
You should not use a stepwise OAuth vulnerability testing approach when concrete validation gates cannot confirm exploitability before reporting, as deterministic discovery inputs and explicit attack-surface signals are required.
Kisilev13Scan web applications for OAuth vulnerabilities and generate detailed reports.
EntroVyxIdentify OAuth 2.0 and OIDC vulnerabilities in web and mobile applications.
lNwNlIdentify OAuth 2.0 and OpenID Connect misconfiguration risks in authorization flows.
pdparchitectIdentify and validate authentication bypass vulnerabilities across SSO, SAML, OAuth, JWT, and legacy endpoints.