Offensive API Security
Comprehensive API security testing methodology covering REST, gRPC, and WebSocket...
Install
npx skills add SnailSploit/Claude-Red --skill offensive-api-security -g -a claude-code -y- Repository
- SnailSploit/Claude-Red10.2k
- Category
- Design
- Updated
- 23d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Comprehensive API security testing methodology covering REST, gRPC, and WebSocket attack surfaces. Addresses the full OWASP API Security Top 10 2023 including BOLA/IDOR, broken authentication, excessive data exposure, rate limiting bypass, BFLA, mass assignment, SSRF, and security misconfiguration. Includes REST-specific attacks such as HTTP verb tampering, content-type switching, and parameter pollution. Covers gRPC exploitation through protobuf interception, reflection API enumeration, and metadata injection. Addresses WebSocket vulnerabilities including origin bypass, message injection, and cross-site WebSocket hijacking. Provides tooling guidance for Burp Suite, Postman, grpcurl, websocat, and mitmproxy. Each technique includes detection signatures and defensive indicators so you understand what artifacts your testing leaves behind. Designed for authorized penetration testing engagements against API-driven architectures.
Offensive API Security Testing
You are conducting authorized security assessments against API-driven applications. This skill covers REST, gRPC, and WebSocket attack surfaces with emphasis on the OWASP API Security Top 10 2023. Every technique assumes you have written authorization and a defined scope. Your goal is to identify vulnerabilities that allow unauthorized data access, privilege escalation, or service disruption through API-layer attacks.
Quick Workflow
- Map the API surface: collect OpenAPI/Swagger specs, gRPC reflection output, and WebSocket endpoints.
- Enumerate authentication mechanisms: API keys, OAuth flows, JWTs, session tokens.
- Test BOLA/IDOR by substituting object identifiers across authenticated contexts.
- Probe authorization boundaries with BFLA checks across roles and HTTP methods.
- Fuzz parameters for mass assignment, content-type switching, and verb tampering.
- Assess rate limiting and resource consumption controls.
- Test gRPC-specific vectors: reflection enumeration, metadata injection, protobuf manipulation.
- Evaluate WebSocket security: origin validation, message integrity, CSWSH.
- Check for SSRF via URL-accepting parameters and webhook configurations.
- Document findings with reproduction steps and severity ratings.
OWASP API Top 10 2023 -- BOLA and IDOR
Broken Object Level Authorization (BOLA) is the most prevalent API vulnerability. You test it by capturing a legitimate request containing an object identifier and replaying it with identifiers belonging to other users or tenants.
GET /api/v1/users/1001/orders HTTP/1.1
Authorization: Bearer eyJhbGciOi...user_a_token
Host: target.example.com
Replay with a different user ID while retaining the original token:
GET /api/v1/users/1002/orders HTTP/1.1
Authorization: Bearer eyJhbGciOi...user_a_token
Host: target.example.com
Automate IDOR testing across sequential and UUID-based identifiers:
