Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/api-graphqlAPIs, SaaS and identity

api-graphql

⁨Attack GraphQL APIs. Load on /graphql, /graphiql, /v1/graphql, a POST with {"query":"..."}, Apollo/Hasura/graphene stacks, or "query/mutation" language. Signals: introspection enabled, batched queries, deeply nested fields, __schema, aliases.⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/api-graphql

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
6ABbI4stFP…/RhqwvAw==The CLI checks the SHA-256 and the signature before it writes a file.
Packagef059c6c8…0787518e
f059c6c8f0f5…9d900787518e2 files · ⁦2.6 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-graphql@ee0e0c5

When it applies

The target exposes a GraphQL endpoint. GraphQL collapses many objects behind one URL, so authorization gaps and info leaks are common and easy to miss with URL-based testing.

Why it works

One endpoint, a self-describing schema, and per-field resolvers mean access control must be enforced at every field/resolver — it frequently isn't. Introspection hands you the entire attack surface; batching/aliases turn one request into thousands.

Method

  1. Fingerprint & map: graphw00f for the engine; if introspection is on, dump the schema ({__schema{types{name fields{name}}}}) with inql/clairvoyance. If off, brute field names with clairvoyance (error messages leak valid fields).
  2. AuthZ testing (BOLA/BFLA): call queries/mutations for objects and admin operations you shouldn't reach; swap ids in arguments (same as IDOR) — resolvers often skip owner checks.
  3. Info disclosure: reach sensitive fields/types (users, tokens, internal flags) via nested relations even when the "front door" query hides them.
  4. DoS / cost: deeply nested recursive queries and aliased batching (a:login b:login ...) to bypass rate limits or brute-force — respect program rules on this.
  5. Injection: arguments feed backends — test SQLi/NoSQLi in GraphQL variable values.

Gotchas

  • Introspection off ≠ safe — field brute-forcing and suggestion errors still map the schema.
  • Rate-limit bypass via batching/aliases is a real, reportable finding on many programs.
  • Mutations are where impact lives; don't stop at read queries.

Verify success

Retrieve/modify data through a query or mutation your role shouldn't allow, or dump a schema that reveals hidden admin operations.

References

PortSwigger GraphQL labs; OWASP API Security Top 10 (2023); graphw00f/inql docs.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5f059c6c8Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login