oauth-flow-hijack SKILL.md skillA
oauth-flow-hijack from dreadnode/capabilities is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dreadnode/capabilities/oauth-flow-hijack@git:20260504.2a64374Pins git:20260504.2a64374 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dreadnode/capabilities
- Path
capabilities/web-security/skills/oauth-flow-hijack/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260504.2a64374, committed May 4, 2026
- Size
- 7,119 bytes
- Repository stars
- 22
- License
- MIT
Techniques to hijack OAuth flows by stopping redirects, leaking authorization codes, and exploiting popup or iframe name collisions. Use when testing OAuth implementations, especially when you have XSS on a subdomain, an open redirect, or a way to prevent callback consumption.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# OAuth Flow Hijack Techniques ## 1. Stopping Client-Side Redirects ### Navigation rate limiting Some browser versions throttle excessive navigations. If the target relies on client-side redirects, throttling can leave the callback page rendered with the code still present in the URL. ### Sandboxed frame without `allow-forms` Load the target in a sandbox that permits scripts but blocks form submission. This can break automatic callback completion logic while still allowing attacker-controlled JavaScript contexts nearby. ### Dangling markup in URL Certain browser behaviors treat malformed client-side navigation targets as blocked. If part of the redirect URL is attacker-influenced, malformed fragments can stop the navigation. ### URL overflow Large `state` values can trigger 414, 431, or 500 responses before the authorization code is consumed. ## 2. Leaking Authorization Codes ### Navigation API history leak After forcing an error state, redirect to a readable origin such as `about:blank` and inspect navigation history where available. ### Cookie bombing -> 431 Oversized cookies scoped to the callback path can force a 431 response, leaving the code unconsumed. …
Read the whole file at its exact version.
How to install
mdr add dreadnode/capabilities/oauth-flow-hijack@sha256:53b0faa106fbaadaThe line at the top of this page pins the label git:20260504.2a64374, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t7i3icoop3qnzln7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 4, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7119 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
dreadnode/capabilities · 22 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t7i3icoop3qnzln7 GET https://markdownregistry.com/api/v1/resolve?ref=dreadnode/capabilities/oauth-flow-hijack GET https://markdownregistry.com/api/v1/blob/53b0faa106fbaada52f1547b100fb92f62279ee1002a553232316bbdb7cc26bb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.