Individual skill
offensive-api-abuse
Advanced API exploitation methodology focused on business logic abuse and sophisticated attack patterns that bypass traditional security controls. Covers business logic bypass through API call chaining and workflow manipulation. Addresses GraphQL-specific attacks including batching for credential brute-force, query depth exploitation, and introspection abuse. Includes pagination exploitation for data exfiltration, webhook hijacking for SSRF and data interception, and resource exhaustion through algorithmic complexity attacks. Covers race conditions in API transactions using parallel request techniques. Provides comprehensive JWT manipulation including algorithm confusion, kid injection, jku/x5u abuse, and claim tampering. Details API key leakage detection across source repositories, client-side code, and error messages. Covers undocumented endpoint discovery through predictable naming, debug routes, and source map analysis. Tooling includes Arjun, ParamSpider, jwt_tool, and GraphQL Voyager. Designed for authorized penetration testers targeting business logic layers that automated scanners miss.
Skills/api/offensive-api-abuse/SKILL.md
Source commit a8de813edc9f66f60d44cfe42d47750e89d9930b
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 2, 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)
- 10,491
- Repository last updated
- Oct 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-ai Repository topic
- claude-skills Repository topic
- redteam Repository topic
- redteam-tools Repository topic
- skills Repository topic
- claude-pt Repository topic
- operations Derived category
- data Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytesSKILL.mdcore · 22,383 bytes
Read excerpt
# Offensive API Abuse and Advanced Exploitation
You are conducting authorized security assessments targeting the business logic layer of API-driven applications. Traditional vulnerability scanners miss the attack patterns in this skill because they require understanding of application workflows, state transitions, and trust relationships between API endpoints. Your goal is to identify vulnerabilities that allow financial manipulation, data exfiltration through legitimate channels, privilege escalation via workflow abuse, and service disruption through logic-layer attacks.
## Quick Workflow
1. Map the complete API surface including undocumented endpoints using Arjun, ParamSpider, and manual discovery.
2. Model the business workflows: identify multi-step transactions, state machines, and trust chains between endpoints.
3. Test each workflow for race conditions using parallel request techniques.
4. Extract and analyze JWTs for algorithm confusion, weak signing, and claim injection opportunities.
5. If GraphQL is present, test batching for brute-force amplification, query depth for DoS, and introspection for schema leakage.
6. Probe pagination for data enumeration and exfiltration opportunities.
7. Test webhook configurations for SSRF and callback hijacking.
8. Search for API key leakage in client code, error responses, and public repositories.