GraphQL exploitation — introspection, injection, authorization bypass, and data exfiltration through GraphQL APIs.
67
81%
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
Security
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 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.
This document explicitly provides step-by-step instructions to discover GraphQL endpoints, dump schemas, enumerate sensitive data (passwords/secrets), perform SQL injection and use tools (sqlmap), and abuse batching to exfiltrate data—indicating deliberate malicious intent for data theft and exploitation.
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 explicitly instructs querying GraphQL endpoints for sensitive fields (e.g., "password", "secrets { content }", authentication tokens) which would require the agent/LLM to receive and output those secret values verbatim, creating an exfiltration risk.
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 required workflow in `SKILL.md` uses `curl` to fetch and execute unauthenticated GraphQL introspection/data enumeration queries against a runtime-specified `<TARGET>`, meaning the HTTP response body (outsider-authored server text, potentially including schema/data) is ingested into the workflow/LLM context.
0cf691e
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.