Overview
A finding earns a place in the report only after it has a deterministic reproduction path and a demonstrated business impact. Multi-phase testing — passive/active reconnaissance, target surface mapping, API protocol fuzzing, binary and script reverse engineering, multi-vulnerability exploit chaining — exists to produce findings that clear that bar.
[Phase 1: Scope & Reconnaissance] ──► [Phase 2: Vulnerability Hunting & Fuzzing] ──► [Phase 3: Reverse Engineering]
│
[Phase 5: Proof & Report Delivery] ◄── [Phase 4: Exploit Chaining] ◄────────────────┘
The penetration tester operates strictly within authorized rules of engagement, validates proof-of-concept exploits without causing Denial of Service or data loss, and chains low-severity findings into demonstrable business impact.
When to Use
- When conducting authorized penetration tests against web applications, APIs, or cloud platforms.
- When executing time-boxed bug bounty hunts on HackerOne, Bugcrowd, or private programs.
- When performing advanced protocol, parameter, or grammar fuzzing on proprietary binaries and network endpoints.
- When decompiling and reverse engineering compiled binaries, Android APKs, or obfuscated frontend JavaScript bundles.
- When chaining multiple low/medium severity vulnerabilities (e.g. CSRF + CORS + IDOR) into account takeover or RCE.
- When drafting professional penetration test reports with executive summaries, CVSS 3.1 scoring, and remediation steps.
When NOT to Use
- When implementing defensive application code patches or writing production fixes (use
cybersecurity/role-security-engineer).
- When managing CI/CD deployment pipelines or infrastructure orchestration (use
devops/role-devops-sre-engineer).
- When conducting unit or integration regression testing of normal software features (use
development/role-qa-automation-engineer).
- When unauthorized by explicit written rules of engagement or program scope.
Deterministic Dispatch Matrix
| Offensive Engagement Phase / Technique |
Delegated Child Skill |
Primary Offensive Artifact |
| Autonomous multi-tool pentesting orchestration & MCP security tools |
cybersecurity/hexstrike-ai-pentest |
Coordinated scan outputs, target maps, tool logs |
| Systematic web app vulnerability hunting (OWASP Top 10, logic flaws) |
cybersecurity/bug-hunting |
Validated vulnerability PoCs with reproduction steps |
| Advanced parameter, grammar, and memory fuzzing for zero-days |
cybersecurity/fuzz-master |
Fuzzing crash dumps, mutated testcases, exception traces |
| Decompiling binaries, APKs, WASM, and deobfuscating JS bundles |
cybersecurity/reverse-engineering-router |
Reconstructed source models, API endpoints, protocol specs |
| Combining isolated vulnerabilities into high-impact exploit chains |
cybersecurity/bug-chain-builder |
Multi-step exploit chain proof (e.g. Info Leak -> Auth Bypass -> RCE) |
| Generating professional bug bounty & audit vulnerability reports |
cybersecurity/report-generator |
Structured Markdown/PDF security assessment report |
| Authorized external recon & initial access campaigns (A-poc RedTeam-Tools) |
cybersecurity/red-team-recon-and-initial-access |
Recon maps, verified takeover/dangling records, authorized spray/phishing evidence |
| Authorized privilege escalation & AD discovery (A-poc RedTeam-Tools) |
cybersecurity/red-team-privilege-escalation-and-discovery |
PE findings, AD trust/ACL abuse paths, verified canary executions |
| Authorized credential access & lateral movement (A-poc RedTeam-Tools) |
cybersecurity/red-team-credential-access-and-lateral-movement |
Captured credential artifacts, safe lateral movement proofs |
| Payload development, obfuscation & EDR evasion (A-poc RedTeam-Tools) |
cybersecurity/red-team-resource-development-and-evasion |
Lab-validated evasive payloads with kill-switches |
| Authorized exfiltration & safe impact demonstration (A-poc RedTeam-Tools) |
cybersecurity/red-team-exfiltration-and-impact |
Synthetic-data exfil receipts, controlled impact validation |
| Red team tool selection & advisory catalog |
cybersecurity/red-team-tools-catalog |
Tool capability mapping to ATT&CK tactics |
Workflow
Phase 1: Scoping & Reconnaissance
- Verify authorization, target scope, excluded assets, and safe testing boundaries.
- Coordinate reconnaissance tooling via
cybersecurity/hexstrike-ai-pentest (subdomain discovery, port mapping, technology stack fingerprinting).
- Map authenticated and unauthenticated attack surfaces.
Phase 2: Vulnerability Hunting & Protocol Fuzzing
- Dispatch to
cybersecurity/bug-hunting for systematic testing of business logic, access control, and injection vectors.
- For binary parsers or custom RPC protocols, dispatch to
cybersecurity/fuzz-master to deliver mutated inputs and detect crashes.
- Record all anomalous responses, timing variations, and verbose error envelopes.
Phase 3: Deep Reverse Engineering & Protocol Dissection
- When analyzing client-side binaries, mobile applications, or obfuscated SPA bundles, dispatch to
cybersecurity/reverse-engineering-router.
- Extract hidden API endpoints, cryptographic keys, request signing routines, and undocumented parameters.
- Validate client-side restrictions and identify missing server-side authorization checks.
Phase 4: Exploit Chaining & Impact Demonstration
- Dispatch to
cybersecurity/bug-chain-builder to correlate isolated low/medium severity defects.
- Construct deterministic multi-stage exploit chains demonstrating tangible business impact (e.g. Account Takeover, Privilege Escalation, Remote Code Execution).
- Verify that exploit payloads are benign and non-destructive (e.g. reading harmless canary files or demonstrating state modification safely).
Phase 5: Evidence Packaging & Report Delivery
- Compile reproduction steps, raw HTTP requests/responses, and environmental prerequisites.
- Dispatch to
cybersecurity/report-generator to draft the executive summary, calculate CVSS 3.1 scores, and document precise remediation guidance.
- Deliver the final assessment package adhering to enterprise bug bounty and pentest standards.
Anti-Rationalization Table
| Pentest Excuse |
Flawed Rationalization |
Required Offensive Discipline |
| "Scanner says clean, so target is secure" |
"Automated tools tested all known CVEs." |
Scanners cannot understand custom business logic. Manually probe workflows, race conditions, and role transitions. |
| "This bug is only low severity, ignore it" |
"Self-XSS or info disclosure isn't worth reporting." |
Chain low-severity vulnerabilities together via cybersecurity/bug-chain-builder to prove critical impact. |
| "Run intrusive payloads on production" |
"Testing with destructive drops proves RCE faster." |
Destructive payloads violate ethical boundaries. Always use harmless canaries (whoami, id, touch canary). |
| "Screenshot of the error page is enough PoC" |
"The client can see the stack trace in the image." |
Screenshots without repeatable curl or script reproduction are rejected. Provide deterministic CLI proof. |
| "Skip documenting remediation" |
"The developers should know how to fix their own code." |
Incomplete reports provide zero defensive value. Provide concrete code diffs and architectural fixes. |
Implementation Examples
Reproducible Proof-of-Concept Exploit Harness (Python)
import urllib.request
import urllib.parse
import json
import sys
def verify_idor_vulnerability(target_api: str, attacker_token: str, victim_resource_id: str) -> bool:
"""Demonstrates authorization bypass (IDOR) without data destruction."""
url = f"{target_api}/api/v1/documents/{victim_resource_id}"
headers = {
"Authorization": f"Bearer {attacker_token}",
"User-Agent": "EthicalSecurityTester/1.0",
"Accept": "application/json"
}
req = urllib.request.Request(url, headers=headers, method="GET")
try:
with urllib.request.urlopen(req, timeout=5) as resp:
if resp.status == 200:
body = json.loads(resp.read().decode())
# Verify that resource belongs to another tenant without leaking PII
if "owner_id" in body and body["owner_id"] != "attacker_user":
print(f"CONFIRMED: IDOR vulnerability detected on resource {victim_resource_id}!")
print(f"Status: {resp.status} OK | Leaked Metadata: {list(body.keys())}")
return True
except Exception as e:
print(f"Test safely rejected or target unreachable: {e}")
return False
if __name__ == "__main__":
print("Penetration testing PoC harness initialized.")
Exploit Reproduction Verification Script (Bash)
#!/usr/bin/env bash
set -euo pipefail
TARGET_HOST="https://api.target.internal"
ATTACKER_JWT="eyJhbGciOi..."
RESOURCE_ID="10928"
echo "=== Testing BOLA/IDOR on Target Resource: $RESOURCE_ID ==="
HTTP_RESPONSE=$(curl -s -w "\n%{http_code}" -X GET "$TARGET_HOST/api/v1/records/$RESOURCE_ID" \
-H "Authorization: Bearer $ATTACKER_JWT" \
-H "Content-Type: application/json")
HTTP_STATUS=$(echo "$HTTP_RESPONSE" | tail -n1)
BODY=$(echo "$HTTP_RESPONSE" | head -n -1)
if [ "$HTTP_STATUS" -eq 200 ]; then
echo "CRITICAL: Authorization barrier failed! HTTP 200 received for cross-tenant resource."
echo "Evidence snippet: ${BODY:0:120}..."
exit 0
elif [ "$HTTP_STATUS" -eq 403 ] || [ "$HTTP_STATUS" -eq 404 ]; then
echo "SAFE: Endpoint properly restricted with HTTP $HTTP_STATUS."
exit 1
fi
Verification Checklist
npm install -g cli-tool
1---2name: role-penetration-tester3description: Use when orchestrating offensive security testing, ethical red teaming,4 web vulnerability discovery, API fuzzing, reverse engineering, exploit chaining,5 and bug bounty reporting.6domain: cybersecurity7author: oyi778version: 1.0.09category: cybersecurity10tags:11- security12- pentest13- red-team14- offensive-security15- bug-bounty16license: MIT17subdomain: penetration-testing18triggers:19- pentester role20- pentest engagement21- red team exercise22- bug bounty hunt23- api fuzzing24- exploit chain25- kerberoasting26- privilege escalation audit27metadata:28 source: https://skillmd.com/skills/oyi77/role-penetration-tester29---3031## Overview3233A finding earns a place in the report only after it has a deterministic reproduction path and a demonstrated business impact. Multi-phase testing — passive/active reconnaissance, target surface mapping, API protocol fuzzing, binary and script reverse engineering, multi-vulnerability exploit chaining — exists to produce findings that clear that bar.3435```36[Phase 1: Scope & Reconnaissance] ──► [Phase 2: Vulnerability Hunting & Fuzzing] ──► [Phase 3: Reverse Engineering]37 │38 [Phase 5: Proof & Report Delivery] ◄── [Phase 4: Exploit Chaining] ◄────────────────┘39```4041The penetration tester operates strictly within authorized rules of engagement, validates proof-of-concept exploits without causing Denial of Service or data loss, and chains low-severity findings into demonstrable business impact.4243## When to Use4445- When conducting authorized penetration tests against web applications, APIs, or cloud platforms.46- When executing time-boxed bug bounty hunts on HackerOne, Bugcrowd, or private programs.47- When performing advanced protocol, parameter, or grammar fuzzing on proprietary binaries and network endpoints.48- When decompiling and reverse engineering compiled binaries, Android APKs, or obfuscated frontend JavaScript bundles.49- When chaining multiple low/medium severity vulnerabilities (e.g. CSRF + CORS + IDOR) into account takeover or RCE.50- When drafting professional penetration test reports with executive summaries, CVSS 3.1 scoring, and remediation steps.5152## When NOT to Use5354- When implementing defensive application code patches or writing production fixes (use `cybersecurity/role-security-engineer`).55- When managing CI/CD deployment pipelines or infrastructure orchestration (use `devops/role-devops-sre-engineer`).56- When conducting unit or integration regression testing of normal software features (use `development/role-qa-automation-engineer`).57- When unauthorized by explicit written rules of engagement or program scope.5859## Deterministic Dispatch Matrix6061| Offensive Engagement Phase / Technique | Delegated Child Skill | Primary Offensive Artifact |62|---|---|---|63| Autonomous multi-tool pentesting orchestration & MCP security tools | `cybersecurity/hexstrike-ai-pentest` | Coordinated scan outputs, target maps, tool logs |64| Systematic web app vulnerability hunting (OWASP Top 10, logic flaws) | `cybersecurity/bug-hunting` | Validated vulnerability PoCs with reproduction steps |65| Advanced parameter, grammar, and memory fuzzing for zero-days | `cybersecurity/fuzz-master` | Fuzzing crash dumps, mutated testcases, exception traces |66| Decompiling binaries, APKs, WASM, and deobfuscating JS bundles | `cybersecurity/reverse-engineering-router` | Reconstructed source models, API endpoints, protocol specs |67| Combining isolated vulnerabilities into high-impact exploit chains | `cybersecurity/bug-chain-builder` | Multi-step exploit chain proof (e.g. Info Leak -> Auth Bypass -> RCE) |68| Generating professional bug bounty & audit vulnerability reports | `cybersecurity/report-generator` | Structured Markdown/PDF security assessment report |69| Authorized external recon & initial access campaigns (A-poc RedTeam-Tools) | `cybersecurity/red-team-recon-and-initial-access` | Recon maps, verified takeover/dangling records, authorized spray/phishing evidence |70| Authorized privilege escalation & AD discovery (A-poc RedTeam-Tools) | `cybersecurity/red-team-privilege-escalation-and-discovery` | PE findings, AD trust/ACL abuse paths, verified canary executions |71| Authorized credential access & lateral movement (A-poc RedTeam-Tools) | `cybersecurity/red-team-credential-access-and-lateral-movement` | Captured credential artifacts, safe lateral movement proofs |72| Payload development, obfuscation & EDR evasion (A-poc RedTeam-Tools) | `cybersecurity/red-team-resource-development-and-evasion` | Lab-validated evasive payloads with kill-switches |73| Authorized exfiltration & safe impact demonstration (A-poc RedTeam-Tools) | `cybersecurity/red-team-exfiltration-and-impact` | Synthetic-data exfil receipts, controlled impact validation |74| Red team tool selection & advisory catalog | `cybersecurity/red-team-tools-catalog` | Tool capability mapping to ATT&CK tactics |7576## Workflow7778### Phase 1: Scoping & Reconnaissance79801. Verify authorization, target scope, excluded assets, and safe testing boundaries.812. Coordinate reconnaissance tooling via `cybersecurity/hexstrike-ai-pentest` (subdomain discovery, port mapping, technology stack fingerprinting).823. Map authenticated and unauthenticated attack surfaces.8384### Phase 2: Vulnerability Hunting & Protocol Fuzzing85861. Dispatch to `cybersecurity/bug-hunting` for systematic testing of business logic, access control, and injection vectors.872. For binary parsers or custom RPC protocols, dispatch to `cybersecurity/fuzz-master` to deliver mutated inputs and detect crashes.883. Record all anomalous responses, timing variations, and verbose error envelopes.8990### Phase 3: Deep Reverse Engineering & Protocol Dissection91921. When analyzing client-side binaries, mobile applications, or obfuscated SPA bundles, dispatch to `cybersecurity/reverse-engineering-router`.932. Extract hidden API endpoints, cryptographic keys, request signing routines, and undocumented parameters.943. Validate client-side restrictions and identify missing server-side authorization checks.9596### Phase 4: Exploit Chaining & Impact Demonstration97981. Dispatch to `cybersecurity/bug-chain-builder` to correlate isolated low/medium severity defects.992. Construct deterministic multi-stage exploit chains demonstrating tangible business impact (e.g. Account Takeover, Privilege Escalation, Remote Code Execution).1003. Verify that exploit payloads are benign and non-destructive (e.g. reading harmless canary files or demonstrating state modification safely).101102### Phase 5: Evidence Packaging & Report Delivery1031041. Compile reproduction steps, raw HTTP requests/responses, and environmental prerequisites.1052. Dispatch to `cybersecurity/report-generator` to draft the executive summary, calculate CVSS 3.1 scores, and document precise remediation guidance.1063. Deliver the final assessment package adhering to enterprise bug bounty and pentest standards.107108## Anti-Rationalization Table109110| Pentest Excuse | Flawed Rationalization | Required Offensive Discipline |111|---|---|---|112| "Scanner says clean, so target is secure" | "Automated tools tested all known CVEs." | Scanners cannot understand custom business logic. Manually probe workflows, race conditions, and role transitions. |113| "This bug is only low severity, ignore it" | "Self-XSS or info disclosure isn't worth reporting." | Chain low-severity vulnerabilities together via `cybersecurity/bug-chain-builder` to prove critical impact. |114| "Run intrusive payloads on production" | "Testing with destructive drops proves RCE faster." | Destructive payloads violate ethical boundaries. Always use harmless canaries (`whoami`, `id`, touch canary). |115| "Screenshot of the error page is enough PoC" | "The client can see the stack trace in the image." | Screenshots without repeatable curl or script reproduction are rejected. Provide deterministic CLI proof. |116| "Skip documenting remediation" | "The developers should know how to fix their own code." | Incomplete reports provide zero defensive value. Provide concrete code diffs and architectural fixes. |117118## Implementation Examples119120### Reproducible Proof-of-Concept Exploit Harness (Python)121122```python123import urllib.request124import urllib.parse125import json126import sys127128def verify_idor_vulnerability(target_api: str, attacker_token: str, victim_resource_id: str) -> bool:129 """Demonstrates authorization bypass (IDOR) without data destruction."""130 url = f"{target_api}/api/v1/documents/{victim_resource_id}"131 headers = {132 "Authorization": f"Bearer {attacker_token}",133 "User-Agent": "EthicalSecurityTester/1.0",134 "Accept": "application/json"135 }136 137 req = urllib.request.Request(url, headers=headers, method="GET")138 try:139 with urllib.request.urlopen(req, timeout=5) as resp:140 if resp.status == 200:141 body = json.loads(resp.read().decode())142 # Verify that resource belongs to another tenant without leaking PII143 if "owner_id" in body and body["owner_id"] != "attacker_user":144 print(f"CONFIRMED: IDOR vulnerability detected on resource {victim_resource_id}!")145 print(f"Status: {resp.status} OK | Leaked Metadata: {list(body.keys())}")146 return True147 except Exception as e:148 print(f"Test safely rejected or target unreachable: {e}")149 150 return False151152if __name__ == "__main__":153 print("Penetration testing PoC harness initialized.")154```155156### Exploit Reproduction Verification Script (Bash)157158```bash159#!/usr/bin/env bash160set -euo pipefail161162TARGET_HOST="https://api.target.internal"163ATTACKER_JWT="eyJhbGciOi..."164RESOURCE_ID="10928"165166echo "=== Testing BOLA/IDOR on Target Resource: $RESOURCE_ID ==="167HTTP_RESPONSE=$(curl -s -w "\n%{http_code}" -X GET "$TARGET_HOST/api/v1/records/$RESOURCE_ID" \168 -H "Authorization: Bearer $ATTACKER_JWT" \169 -H "Content-Type: application/json")170171HTTP_STATUS=$(echo "$HTTP_RESPONSE" | tail -n1)172BODY=$(echo "$HTTP_RESPONSE" | head -n -1)173174if [ "$HTTP_STATUS" -eq 200 ]; then175 echo "CRITICAL: Authorization barrier failed! HTTP 200 received for cross-tenant resource."176 echo "Evidence snippet: ${BODY:0:120}..."177 exit 0178elif [ "$HTTP_STATUS" -eq 403 ] || [ "$HTTP_STATUS" -eq 404 ]; then179 echo "SAFE: Endpoint properly restricted with HTTP $HTTP_STATUS."180 exit 1181fi182```183184## Verification Checklist185186- [ ] Written authorization and scope boundaries confirmed before testing.187- [ ] Automated and manual vulnerability hunting executed without service disruption.188- [ ] Binary, mobile, or web assets reverse-engineered to identify undocumented API surfaces.189- [ ] Isolated vulnerabilities chained to demonstrate tangible business risk.190- [ ] Proof of concept adheres to safe, non-destructive validation principles.191- [ ] Comprehensive penetration test report compiled with CVSS metrics and remediation diffs.192193`npm install -g cli-tool`