elementalsouls/Claude-BugHunter · 22 Nov 2026 · Feature

681 Disclosed Reports, One Interrogation Gate

Omar Haddad
Omar Haddad
Editor-at-Large

Claude-BugHunter turns a general-purpose coding agent into a red-team operator by betting that discipline, not payloads, is what hunters actually lack.

elementalsouls/Claude-BugHunter
★16.2k stars Velocity · 7d +1490 ★/day ↗accelerating
star history

Every few months, a repository appears that treats an LLM agent the way a sysadmin treats a fresh server: as something to be provisioned with a job. Claude-BugHunter is the security-flavored version of that instinct. It’s a bundle of skill files — Markdown documents that Claude Code loads on demand — that together attempt to turn Anthropic’s coding agent into a bug-hunting researcher and external red-team operator. By the time third-party catalogs picked it up, it had accumulated roughly 15,000 stars and 1,749 forks on GitHub, which for a niche offensive-security tooling repo is a loud signal that something in the AI-assisted-hunting crowd has shifted.

elementalsouls/Claude-BugHunter

The interesting question is not whether an LLM can recite XSS payloads. It can, and so can a search engine. The interesting question is what this repo’s author, Sachin Sharma (“elementalsouls”), believes is actually missing from AI-assisted hunting — and the answer, baked into the architecture, is unusual: the repo’s most load-bearing component isn’t an attack technique at all. It’s a refusal mechanism.

The skill-bundle bet

The dominant pattern for AI security assistants is a single large system prompt that says, in effect, “you are a pentester.” A Medium write-up in the Agent Native publication articulates why that pattern fails: when discovery, exploitation, and reporting all live in one conversational loop, assumptions get buried as the conversation grows, and unverified leads start being treated as confirmed findings. The conversation becomes its own epistemic hazard.

Claude-BugHunter’s answer is decomposition. Instead of one prompt, the repo ships dozens of self-contained skill files, each scoped to a purpose: a hunt-idor skill for broken object-level authorization, a triage-validation skill for pre-submission interrogation, an evidence-hygiene skill for redacting cookies and PII from screenshots, a report-writing skill templated per platform. Skills load when their descriptions match what you’re describing to the agent — you talk about a numeric ID in a URL, and the IDOR skill activates. Knowledge stays organized by purpose, context consumption stays bounded, and each specialized behavior remains a file you can open and read.

This is, structurally, glue code — but glue of a deliberate kind. The repo is honest about its lineage: eight of its skills and all fifteen slash commands are vendored from shuvonsec/claude-bug-bounty, an upstream community project, and the per-class hunt skills were scaffolded using that author’s public-skills-builder tool. The credits file says so plainly. What Sharma added on top is the part that carries the repo’s identity: an enterprise-platform attack layer and a red-team discipline layer, both attributed to “authorized engagements” rather than public report mining.

The corpus, and why curation beats generation

The web-application layer is built from 681 disclosed HackerOne reports, distributed across 24 vulnerability classes — 174 for XSS, 67 for RCE, 26 for IDOR, 225 in a catch-all miscellaneous bucket. The third-party SkillsLLM catalog listing notes that 433 of those patterns are individually cited and auditable, which is the detail that matters: these aren’t hallucinated techniques, they’re chain templates that real triagers actually paid for.

That distinction is the repo’s quiet thesis about LLMs. A general model knows what SSRF is in the abstract; it has read the OWASP page. What it doesn’t reliably know is which SSRF variants survived WAFs on real targets, which IDOR patterns triagers accepted versus rejected, and which “findings” are famous wastes of everyone’s time. Curating disclosed reports into per-class pattern libraries is a way of importing survivorship-filtered field data into a model that would otherwise reason from textbook definitions. It’s the difference between a medical student and a residency.

The enterprise layer extends the same idea to perimeter infrastructure: M365/Entra ID attack chains with AADSTS error-code references, Okta tenant enumeration and push-fatigue patterns, on-prem SharePoint including the 2025 ToolShell precondition chain, VMware vCenter CVE progressions, SSL VPN appliances across seven vendors, and an Android APK pipeline. Several of these are marked as derived from authorized engagement work rather than public sources — which is either the repo’s most valuable proprietary content or its least verifiable, depending on how much you trust an author’s self-reporting. The repo offers no way to check that provenance independently, and honest coverage should say so.

The gate

Here is the boring part, which is where the value lives. Before any report gets drafted, every candidate finding must pass what the repo calls the 7-Question Gate: Can an attacker use this right now with a real HTTP request? Is the impact on the program’s accepted-impact list? Is the asset in scope? Does it work without privileged access? Is it not already known? Can impact be proved beyond “technically possible”? Is it not on the never-submit list?

One “no” kills the lead. The gate has four verdicts — PASS, DOWNGRADE, KILL, and CHAIN REQUIRED — and the fourth is genuinely clever. Many high-severity findings only become critical when chained (user enumeration plus missing rate limit plus weak password policy equals account takeover), so “CHAIN REQUIRED” sends the hunter back out to find the other half of the exploit rather than filing a weak report that will die in triage. The README reports this as the single most useful step among researchers who used the bundle, and it aligns with something the broader community keeps rediscovering: as one LinkedIn discussion puts it, consistency and disciplined methodology, not luck, separate top hunters from the noise.

The gate is essentially a formalized answer to the N/A problem — the flood of rejected reports that plagues both new hunters and, increasingly, AI-assisted ones. A recent systematic review of AI in penetration testing notes that most AI pentesting research concentrates on discovery and exploitation, the phases where automation is easiest, while validation and reporting remain underdeveloped. Claude-BugHunter inverts that emphasis. Its payloads are borrowed; its discipline is original.

There’s a parallel in the commercial world. Synack’s AI pentesting platform runs autonomous agent swarms for discovery but routes everything through human Red Team validation before delivery — the same discover-then-validate split, executed with a payroll. Claude-BugHunter is the solo-hunter version: the LLM does the pattern-matching, and the gate does the gatekeeping.

What it refuses to do

The scope section is the most refreshing part of the README, because it’s mostly a list of things the bundle will not help with. Internal Active Directory attacks — BloodHound, Kerberoasting, DCSync — are explicitly out. C2 frameworks, post-exploitation, persistence, EDR evasion: all out, all labeled as design decisions rather than gaps, with the stated rationale that they carry a different operational risk profile. The external-to-internal handoff (Impacket, NetExec, Rubeus, Certify) is deliberately left at the perimeter.

This is unusual candor for a security repo, where the gravitational pull is always toward claiming more capability. It also has a practical function: an agent that “knows” Kerberoasting but lacks the judgment for domain-internal operations is a liability, and walling it off is safer than shipping it half-trained. The authorization posture is similarly explicit — the bundle targets owned or authorized assets, and the triage gate itself asks about scope as questions two and three, making scope-checking a runtime behavior rather than a README disclaimer.

The arms race it rides

The repo’s popularity isn’t happening in a vacuum. HackerOne’s own positioning paper argues that attackers are already using generative AI and automation to outpace defenses, and that offensive security needs a layered AI-plus-human model. Bugcrowd launched AI penetration testing services covering prompt injection, excessive agency, and training-data leakage — noting, via researcher Joseph Thacker, that even security-conscious teams are seeing more vulnerabilities in AI products than usual. And YesWeHack’s analysis of bug bounty’s evolution identifies a two-front squeeze: AI behavior makes vulnerabilities harder to reproduce and validate, while AI-assisted attackers compress the exploitation window.

Claude-BugHunter sits precisely at that squeeze. Its hunt-llm-ai skill covers prompt injection and the ASI01–ASI10 agentic-attack taxonomy — the bundle hunts AI systems and is itself an AI system, which is either recursive or ironic depending on your mood. More consequentially, the economics it encodes are arms-race economics: if your competitors are using an agent that has internalized 681 paid report patterns and refuses to file junk, the marginal value of not using one grows. The repo’s fork count suggests a lot of people reached that conclusion simultaneously.

Rough edges

The repo is moving fast enough to contradict its own documentation. The README describes 51 skills; the SkillsLLM listing and a second catalog both count 83 SKILL.md files at recent commits. Either the README is stale or the catalogs caught a growth spurt — probably both, but a reader can’t tell which, and skill-count inflation is exactly the kind of metric that drifts untethered from reality in hyped repos.

Other caveats are structural. “Battle-tested across authorized engagements” is self-attested; the training-platform validation (DVWA, Juice Shop, Hacker101) is real but those are deliberately vulnerable targets, which is a low bar. The two Reddit threads that presumably contain practitioner skepticism — one literally titled “Expectations and Reality of Claude Code for Bug Bounty” — were inaccessible behind login walls, so the community’s critical voice is missing from this picture. And the deeper limitation is the one the arXiv review flags for the whole field: LLM-driven pentesting remains under-researched for reconnaissance and post-exploitation, and models lack flexibility outside the discovery/exploitation sweet spot. A skill bundle can import pattern libraries; it cannot import the judgment that tells you when the patterns don’t apply.

Outlook

The roadmap is telling in both directions. Planned additions — a HackerOne MCP integration, per-engagement memory across targets, industry-specific hunt skills for fintech GraphQL and healthcare FHIR, a program-rules parser — are all workflow-deepening moves, consistent with the repo’s thesis that coordination and discipline are the bottleneck. The planned ad-cs-attack skill quietly walks back the “internal AD is a different bundle” line, which suggests the external-only perimeter is more of a current release boundary than a philosophical commitment.

The open question is durability. Pattern libraries curated from disclosed reports decay as platforms patch and triage norms shift; the repo acknowledges this with a planned refresh of the hunt skills and quarterly CVE-matrix updates, plus a CISA KEV refresh script that already exists. Whether a solo-maintained corpus can keep pace with an arms race that HackerOne’s paper describes as accelerating is genuinely uncertain.

But the core insight should outlast any particular CVE list. The repo’s closing line — “give Claude the right skill and it stops being a chatbot; it becomes an operator” — is half right. The skills make it knowledgeable. The gate is what makes it an operator, because an operator’s defining trait isn’t knowing the techniques. It’s knowing when not to file the report.

Sources

  1. AI-Augmented Offensive Security for the Modern Threat Landscape
  2. The Role of AI in Modern Penetration Testing
  3. Claude Bug Hunter - Agent Native - Medium
  4. AI in Bug Bounty: AI-Assisted Hunters and Future of Offensive Security
  5. AI Pentesting Platform with Human Validation
  6. Claude-BugHunter - Testing on GitHub (13.3k★)
  7. The AI Era Is Creating a Bug-Hunting Arms Race
  8. Pentesting and AI : r/cybersecurity
  9. Expectations and Reality of Claude Code for Bug Bounty : r/bugbounty
  10. The evolution of Bug Bounty: history, best practices & impact of AI
  11. AI Penetration Testing: Methodology and Scope
  12. Claude BugHunter Bug Bounty Skills

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.