offensive-api-abuse

# 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. 9. Verify all discovered endpoints for authorization consistency. 10. Document business impact for each finding with financial or oper...