Hunting skill for oauth vulnerabilities. Built from 19 public bug bounty reports. Use when hunting oauth on any target.
56
65%
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
2 findings: 1 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
Detected a prompt injection in the skill instructions. The skill contains hidden or deceptive instructions that fall outside its stated purpose and attempt to override the agent’s safety guidelines or intended behavior.
The document contains explicit, actionable exploit instructions and payloads for stealing OAuth tokens and achieving account takeover, i.e., clearly malicious exploit guidance.
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.
The skill contains multiple examples and instructions that capture, reuse, or embed client_secrets, passwords, and access tokens directly in curl commands and scripts (e.g., posting client_secret, using password=value, and reusing $TOKEN in Authorization headers), which requires the LLM/agent to handle and output secret values verbatim.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill’s runtime path is described as a vulnerability-hunting methodology over arbitrary target web/app assets (e.g., “Spider the app”, “Decompile mobile APKs”, “Check .well-known”, “In Burp history”) rather than ingestion of outsider-authored free text from a queue/feed or ticket/email/support/chat source without selecting a specific item.
a3ea443
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.