hunt-oauth
Hunting skill for oauth vulnerabilities. Built from 19 public bug bounty reports. Use when hunting oauth on any target.
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/hunt-oauth/SKILL.mdSecurity
3 findings: 2 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E005: Suspicious download URL detected in skill instructions.
What this means
Detected a suspicious URL in the skill instructions that could lead the agent to download and execute malicious scripts or binaries. This includes links to executables from untrusted sources, typosquatting of official packages, URL shorteners that obscure the destination, and personal file hosting services.
Why it was flagged
Many of the listed URLs contain attacker-controlled domains, host‑confusion / IDN homograph patterns, or open‑redirect payloads (evil.com, attacker.tld, oauth.šemrush.com, legit.com.evil.com, etc.) that are high‑risk for token theft, redirecting to attacker hosts, or delivering malicious payloads — treat them as suspicious.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
This document is an explicit offensive playbook that instructs how to steal OAuth tokens, perform account takeover, and exfiltrate credentials — it is intentionally malicious in purpose and content.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill explicitly shows and instructs embedding captured secrets/tokens/credentials (e.g., CAPTURED_CODE, access_token, client_secret, password) into curl/PoC commands, which would require the LLM to handle or emit secret values verbatim.
- Repository
- elementalsouls/Claude-BugHunter
- Commit
6b9c96e
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.