Skip to main content
skill CX Codex

hunt-forgot-password — Claude Code skill for password reset testing

The hunt-forgot-password skill checks account recovery flows for token leaks, replay, and missing request limits. Use it when auditing a password reset feature.

MIT ★ 16,193 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsouls
Open on GitHub

What hunt-forgot-password does

The skill guides checks for differences between responses to known and unknown email addresses, reset tokens exposed in API responses, and tokens that still work after use. It also covers links that work from another browser or IP, plus repeated reset requests without a limit.

Trace the full recovery flow, from requesting a reset to using its token. For JSON APIs, send requests in the format they accept; use application/x-www-form-urlencoded only for a traditional HTML form. An endpoint without request limits can allow token guessing or inbox flooding.

This skill focuses on individual recovery-flow flaws. hunt-ato covers assembling a full account-takeover chain, while hunt-cache-poison handles host-header injection during reset email generation.

What it helps with

  • compare reset responses for known and unknown email addresses
  • find reset tokens returned in API responses
  • test whether a consumed token works again
  • check whether reset links are tied to an IP or browser
  • detect reset endpoints without request limits

Example prompts for the agent

  • Check whether password reset responses differ for a real and an unknown email address.
  • Look for a reset token in the API response and test whether it can be reused.
  • Test a reset link from another browser and check whether repeated requests are limited.

How to install hunt-forgot-password

1Plugin marketplace

/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsouls

This installs the whole claude-bughunter plugin with all its skills

2Skills CLI (Vercel)

npx skills add elementalsouls/Claude-BugHunter --skill hunt-forgot-password -a claude-code

3Manually: put the files in place

~/.claude/skills/hunt-forgot-password/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hunt-forgot-password/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hunt-forgot-password

How do I install hunt-forgot-password in Claude Code?

Run /plugin marketplace add elementalsouls/Claude-BugHunter first, then run /plugin install claude-bughunter@elementalsouls.

What does hunt-forgot-password do?

It checks account recovery for user enumeration, exposed or reusable reset tokens, links without browser or IP binding, and missing request limits.

How can I test whether a reset token is tied to a browser or IP?

Request a reset link, then try using it from another browser or IP. If it still works, the link is not restricted to the original context.

Source text

SKILL.md · MIT
---
name: hunt-forgot-password
description: "Hunt Forgot Password / Account Recovery Authentication Flaws — 5 distinct patterns: (1) username enumeration via different responses for valid vs invalid email, (2) reset token exposed directly in the API response body, (3) reset token not invalidated after use (replay), (4) password reset link works from a different IP/browser (no binding), (5) no rate limit on the reset request endpoint. These are the standalone recovery-flow broken-auth primitives — distinct from reset-email host-header poisoning (hunt-host-header) and the full ATO chain (hunt-ato owns password-reset as an ATO path; prove the primitive here, chain it there). Detection: trace the full forgot-password flow from request to token to use; check response diffs between valid/invalid emails; test token replay after consumption. Medium to High (enumeration=Medium, token-reuse=High, account-takeover=Critical when chained to known-email)."
sources: hackerone_public, public_research
report_count: 6
---

## Autonomous Testing Priority

**Start with username enumeration — it's the fastest win and gates the rest.**

**Pattern 1 — Username enumeration (response difference for valid vs invalid email):**
1. POST to the forgot-password endpoint with a clearly invalid email (e.g. `[email protected]`) — record the response body, status code, and length
2. POST with an email you know exists (or try common patterns like `[email protected]`, `[email protected]`, `[email protected]`)
3. Compare responses: different message ("Email sent" vs "Email not found"), different HTTP status, or meaningfully different body length = username enumeration confirmed
4. Proof: enumeration is confirmed when the two responses differ measurably (baseline vs probe) in message text, status code, or body length

**Pattern 2 — Reset token exposed in the API response:**
Some APIs return the reset token directly in the response body (instead of only emailing it). POST to the forgot-password endpoint and look for a token, link, or code in the JSON/HTML response. If a token appears that lets you reset the password, that's an immediate account-takeover vector.

**Pattern 3 — Reset token replay (reuse after use):**
1. Complete a full password reset cycle: request token → use it to reset password
2. Immediately try submitting the same token again to the reset-password endpoint
3. If the second submission returns 200 or "success" → token not invalidated after use

**Pattern 4 — No rate limit on reset requests:**
Submit the forgot-password endpoint 10-20 times rapidly with the same email. If all succeed without a 429, lockout, or CAPTCHA → no rate limit (enumeration + token flooding is possible).

**Content-type:** Forgot-password endpoints are often JSON-based REST APIs. Use `application/x-www-form-urlencoded` only if the endpoint is a traditional HTML form (check the login page's HTML to determine form encoding).

**Proof:** Username enumeration = measurably different response (body/status/length). Token exposure = token in response body. Token replay = second successful use of a consumed token.

---

## Vulnerability Classes in This Skill

### 1. Username Enumeration via Password Reset
Different error messages for valid vs invalid accounts leaks the user list without authentication. Even timing differences (fast "no user found" vs slow "email queued") count.

High-value targets: admin accounts, employee email patterns, API keys derived from usernames.

### 2. Weak / Predictable Reset Tokens
A reset token derived from timestamp, username, or sequential IDs can be brute-forced:
- `base64(email + timestamp)` — decodable
- 4-6 digit numeric code — 10K guesses, easily feasible with no rate limit
- Sequential `token=1234`, `token=1235` — trivially enumerable

### 3. Token Not Bound to Session or IP
Most apps generate a token, email it, and accept it from any browser. A truly bound token should only work from the same IP or require the original session cookie. If neither is enforced → link forwarding = account takeover.

**Token leak via `Referer` / third-party resources.** When the token rides in the reset-page URL (`/reset?token=…`) and that page loads any cross-origin resource (analytics, ads, fonts, a CDN image), the full URL — token included — leaks to that third party in the `Referer` header. Check the reset page's outbound requests: if the token appears in any cross-origin `Referer`, it's harvestable without the victim's inbox. Same leak via a `<meta name=referrer>` misconfig or an outbound link the victim clicks from the reset page. Disclosed token-leak→ATO class: <https://hackerone.com/reports/173551>.

### 4. Reset Link Doesn't Expire
Common best practice: reset tokens expire within ~15–60 minutes (no hard RFC mandates the exact value; OWASP recommends a short, single-use lifetime). If a token from 24 hours ago still works → persistence risk for phishing attacks.

### 5. No Rate Limit on Reset Endpoint
An uncapped reset endpoint enables:
- Email flooding (DoS against victim's inbox)
- Token brute-force if the token space is small
- Username enumeration at scale

---

## Related Skills

- **`hunt-ato`** — owns the account-takeover CHAIN (password-reset is its path #1). This skill finds/proves the recovery-flow primitive; hand off to hunt-ato to assemble the full takeover.
- **`hunt-cache-poison`** — host-header injection during reset email generation (different vulnerability, same flow)
- **`hunt-brute-force`** — rate-limit testing pattern applies to the reset endpoint too
- **`hunt-auth-bypass`** — if the reset flow can be skipped entirely (go to `/reset-password?token=` with empty/null token)
- **`hunt-mfa-bypass`** — if MFA is required after reset, test the bypass there

© Sachin Sharma · MIT · elementalsouls/Claude-BugHunter

Similar skills

All skills for Security →

From the same set92

The whole set →
hunt hunt dispatches vulnerability assessments across Red Team and WAPT workflows with scope boundaries. CX Codex +1 ★ 16,193repo stars token-scan token-scan — a Claude slash command that hunts rug-pull vectors in token and meme coin contracts on Solidity and Solana. Useful before you buy an unknown token or ship your own. CX Codex +1 ★ 16,193repo stars chain Takes a confirmed bug A and finds B and C to combine into a higher-severity chain. For bug hunters stuck with Low or conditionally valid findings. CX Codex +1 ★ 16,193repo stars hunt-nosqli hunt-nosqli helps detect NoSQL injection flaws in MongoDB, CouchDB, and Redis. It assists developers and testers during API security reviews and auth auditing. CX Codex +1 ★ 16,193repo stars hunt-deserialization hunt-deserialization — a skill for hunting deserialization bugs in Java, PHP, Python, .NET and Ruby. Tests ysoserial gadget chains, PHP object injection, pickle RCE, BinaryFormatter and Log4Shell. CX Codex +1 ★ 16,193repo stars hunt-captcha-bypass hunt-captcha-bypass is a Claude Code skill that tests web forms and API endpoints for CAPTCHA bypass flaws during security audits of login and registration routes. CX Codex +1 ★ 16,193repo stars web3-audit The web3-audit command checks smart contracts against ten bug classes and helps turn a confirmed issue into a Foundry test. Use it for a structured first pass over Solidity code. CX Codex +1 ★ 16,193repo stars hunt-saml hunt-saml hunts SAML and SSO flaws: XSW, comment injection, signature stripping and XXE in assertions. Built for poking at a live SSO flow. CX Codex +1 ★ 16,193repo stars

Project sponsors

Companies that keep this analytics open