agentleFS
Sign inStart free
NoorQureshiNoorQureshi/SploitAgent/skills/api/api-auth-attacks/SKILL.md

api-auth-attacks

Skill26 starsChanged 31 days agoMITView on GitHub

Break API authentication: token handling, key leakage, weak session/JWT, and no-auth endpoints. Load on REST/GraphQL APIs using API keys, Bearer tokens, HMAC signing, or basic auth. Signals: `Authorization` headers, api_key params, tokens in URLs, /v1 vs /v2 auth drift.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test every version and verb — the fix may exist only on the newest route.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

API authentication attacks

When it applies

An API authenticates requests via tokens/keys/sessions. Auth is the gate; weaknesses here open everything behind it.

Why it works

APIs sprawl (many endpoints, versions, clients) so authentication is applied inconsistently: some routes forgot it, tokens are long-lived or weakly signed, keys leak client-side, and error/timing differences enable enumeration and brute force.

Method

  1. No-auth endpoints: replay requests with the token removed; probe /v1 vs /v2, /internal, /debug, and undocumented routes (Swagger/OpenAPI) for missing auth.
  2. Token weaknesses: JWT issues (→ web-auth-jwt: alg confusion, weak secret, none); long/ non-expiring tokens; predictable session ids; token accepted in URL (logged/leaked).
  3. Key leakage: hunt keys in JS bundles, mobile apps, git (→ code-review-secrets-detection), and test their privilege/scope.
  4. Brute/enumeration: username enumeration via login/reset differences; weak rate limits on login/OTP (→ web-race-conditions for OTP windows).
  5. Auth logic: password reset token predictability/leak, 2FA bypass, "remember me" tokens.

Gotchas

  • Test every version and verb — the fix may exist only on the newest route.
  • A leaked key must be live and privileged to matter — validate scope, don't over-collect.
  • Rate-limit "bypass" via parallelism or header rotation is reportable on many programs.

Verify success

Authenticated access without valid credentials (no-auth route, forged/replayed token, or a live leaked key performing a privileged action).

References

OWASP API Security Top 10 (API2); PortSwigger auth labs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free