Menu

Individual skill

attacking-graphql

0upvotes

Test GraphQL APIs — introspection and schema recovery when introspection is disabled, field suggestion abuse, batching and alias-based rate limit bypass, query depth and complexity denial of service, authorization gaps per field and per resolver, and mutation abuse. Use when a target exposes /graphql, /v1/graphql, or /api/graphql, when requests contain a query or mutation body, or when responses carry a data and errors envelope.

secskills-offense/skills/attacking-graphql/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
188
Repository last updated
Sep 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Attacking GraphQL

GraphQL moves authorization from routes to resolvers, and most teams do not
move their access control with it. The REST habit of protecting `/admin/*` has
no equivalent when every operation arrives at one endpoint — so the recurring
finding is not an exotic GraphQL bug, it is an ordinary authorization failure
on a field nobody thought to guard.

## When to Use

- The target exposes `/graphql`, `/graphiql`, `/v1/graphql`, `/api/graphql`
- Request bodies contain `query`, `mutation`, `subscription`, or `operationName`
- Responses have the `{"data": ..., "errors": [...]}` envelope
- A mobile or SPA client posts GraphQL to a backend
Back to top