Skip to main content
skill CX Codex

hunt-exceptional-conditions — Claude Code skill

The hunt-exceptional-conditions skill reveals when an app leaks stack traces, server paths, or library versions through unhandled exceptions triggered by malformed input. Effective for testing APIs and web endpoints.

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-exceptional-conditions does

The skill teaches you to hunt for information disclosure through error handling. When code receives broken JSON, a field of the wrong type, an oversized value, or a null byte, a well-built app returns a clean error message. A broken one throws an unhandled exception and renders the developer error page to the client: stack trace, ORM query details, server-side file paths, framework and library versions.

You test any input-accepting endpoint—JSON APIs with typed fields, query and path parameters, forms, file uploads. For each request, send variations that violate one assumption: a string instead of a number, an array instead of an object, truncated JSON, a very long value. The signal of a finding appears in the response body: signatures like SequelizeDatabaseError, Traceback (most recent call last), /var/www/.../file.php on line N, Java stack frames, or .NET YSOD.

Structural disclosure typically opens the door to deeper attacks—SQL injection, RCE, or path traversal. The skill requires you to capture the exact leaked artifact (path, ORM class, version, stack frame), not just note a 500 status.

What it helps with

  • detect improper handling of type mismatches and boundary values in APIs
  • uncover server file paths and internal data structure disclosure
  • identify leaks of library and framework versions through error messages
  • find endpoints returning unfiltered stack traces to clients

Example prompts for the agent

  • Send wrong type in rating to /api/feedback and capture the ORM stack trace
  • Post an oversized string in the comment field and watch for stack frames in the error response
  • Test /item/{id} with a null byte, intercept whether the app leaks server paths

How to install hunt-exceptional-conditions

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-exceptional-conditions -a claude-code

3Manually: put the files in place

~/.claude/skills/hunt-exceptional-conditions/SKILL.md

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

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

Questions about hunt-exceptional-conditions

How do I install hunt-exceptional-conditions in Claude Code?

Run /plugin marketplace add elementalsouls/Claude-BugHunter, then /plugin install claude-bughunter@elementalsouls, then npx skills add elementalsouls/Claude-BugHunter --skill hunt-exceptional-conditions -a claude-code. The skill loads into ~/.claude/skills/hunt-exceptional-conditions/SKILL.md.

What does hunt-exceptional-conditions do?

It teaches you to find information disclosure vulnerabilities by triggering unhandled exceptions. When an app receives malformed input and renders a stack trace, internal paths, or library versions, that structural leak can enable further attacks.

Which endpoints should I test?

Any that accept input: JSON APIs with typed fields, query and path parameters, search, filters, sorting, file uploads. Start with a known working request and vary one parameter at a time—send wrong types, truncated JSON, very long strings, boundary values.

Source text

SKILL.md · MIT
---
name: hunt-exceptional-conditions
description: "Hunt mishandling of exceptional conditions — feed an endpoint malformed/unexpected input (wrong type, broken JSON, oversized field, null byte) and make it fail OPEN or leak internals: a verbose stack-trace / framework error page that discloses ORM internals, server file paths, library versions, or a language traceback. Use on any input-accepting endpoint (JSON APIs, forms, query params). Medium-High when the leak exposes internal structure that arms a deeper attack."
report_count: 0
sources: hackerone_public
---

# HUNT-EXCEPTIONAL-CONDITIONS — Verbose Errors / Fail-Open (A10:2025)

## What actually pays

Well-built apps catch errors and return a clean, generic message. A broken app,
when handed input it didn't expect, throws an unhandled exception and renders a
**developer error page** straight to the client — leaking the stack trace, the
ORM/query internals, server-side file paths, and framework/library versions.
That disclosure is the finding (and it arms SQLi/RCE/path attacks next).

## Recon

Any endpoint that parses input is a candidate; the richest are:

```
JSON APIs that expect typed fields:  POST /api/* with {numbers, ids, enums}
Endpoints with numeric/id path or query params:  /item/{id}, ?page=, ?quantity=
Search / filter / sort params
File or content-type sensitive uploads
```

## Attack — send what the code didn't anticipate

Take a known-good request and break ONE assumption at a time:

- **Wrong type:** a field the app expects to be a number/string is sent as an
  array or object — `{"rating":"x","comment":[1,2,3]}`, `{"quantity":{}}`.
- **Malformed body:** truncated/!invalid JSON, an unterminated string, a stray
  brace, a wrong/missing Content-Type.
- **Boundary/oversized:** a very long string, a huge/negative/overflow number.
- **Null byte / control chars** embedded in a value.

```
POST /api/Feedbacks   {"rating":"notanumber","comment":[1,2,3]}
GET  /item/' OR /item/%00   (also exercises the error path)
```

Watch the RESPONSE BODY, not just the status: a 500 (or even a 200/400) whose
body contains a stack trace or framework error page is the signal.

## What counts as a leak (the success signal)

A finding is confirmed when the response body contains a cross-framework error-disclosure signature:

- **Node/Express + Sequelize:** `SequelizeDatabaseError`, `node_modules/sequelize`,
  a JS stack with internal paths.
- **PHP:** `<b>Warning</b> ... /var/www/.../file.php on line N`.
- **Python:** `Traceback (most recent call last)`, `werkzeug.exceptions`.
- **Java:** `at com.app.Foo(Foo.java:42)` stack frames.
- **.NET:** `Server Error in '/' Application`, a `[System.XxxException: ...]` YSOD.

A clean JSON error (`{"error":"Invalid input"}`) with no internals is NOT a
finding — that's correct handling. Disclosure of internal structure is.

## Validation discipline

- Capture the exact leaked artifact (path, ORM class, version, stack frame) —
  that's the evidence. "It returned 500" alone is not disclosure.
- Note what the leak enables next (e.g. a disclosed SQL error → hunt-sqli; a
  disclosed absolute path → hunt-lfi).

© Sachin Sharma · MIT · elementalsouls/Claude-BugHunter

Similar skills

All skills for Security →

From the same set92

The whole set →
memory-gc The memory-gc command checks the autopilot’s JSONL ledgers and rotates files that exceed a size cap. Use it when findings.jsonl or negatives.jsonl keeps growing. CX Codex +1 ★ 16,193repo stars surface Shows a ranked attack surface for a target from its recon manifest and hunt memory. CX Codex +1 ★ 16,193repo stars intel Fetches target intelligence on demand: scans NVD and GitHub advisories, checks HackerOne reports, and flags untested endpoints from hunt memory. CX Codex +1 ★ 16,193repo stars scope scope is a Claude Code command that checks hosts and URLs before active testing. It blocks assets outside engagement rules during security work. CX Codex +1 ★ 16,193repo stars triage triage evaluates security findings through a 7-question gate before you write a bug report. It helps bug bounty hunters discard invalid submissions immediately. CX Codex +1 ★ 16,193repo stars report Builds a submission-ready bug bounty report. Generates CVSS 3.1 score, proof of concept, impact statement, and fix in HackerOne, Bugcrowd, Intigriti, or Immunefi format. CX Codex +1 ★ 16,193repo stars validate validate — a validation command that culls weak findings before report writing. Runs a 7-Question Gate and 4-gate checklist to prevent submissions that damage your validity ratio. CX Codex +1 ★ 16,193repo stars autopilot autopilot is a Claude Code command for autonomous vulnerability hunting. It checks scope, ranks targets, validates findings, and drafts reports. CX Codex +1 ★ 16,193repo stars

Project sponsors

Companies that keep this analytics open