Individual skill
performing-exploit-verification
Systematic methodology for safely confirming and documenting exploited vulnerabilities with reproducible proof, ensuring zero false positives before reporting.
internal/tools/skills/data/penetration-testing/performing-exploit-verification/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 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)
- 1,320
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- penetration-testing Declared skill tag
- exploit-verification Declared skill tag
- proof-of-concept Declared skill tag
- false-positive-elimination Declared skill tag
- vulnerability-confirmation Declared skill tag
- safe-exploitation Declared skill tag
- security Derived category
- testing 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
Read excerpt
# Performing Exploit Verification
## When to Use
- After discovering a potential vulnerability during any scanning or testing phase
- Before calling `report_vulnerability` to prevent false positive reports
- When automated scanners (nuclei, nikto, etc.) flag an issue that needs manual confirmation
- When the initial exploit attempt is ambiguous (e.g., 500 error vs. actual RCE)
- As the final gate before reporting ANY finding to the client
## Most Often Missed & How to Confirm
- **Running the control test, not just the exploit** — the most common false positive is reporting a difference (size, status, timing) without a baseline + control proving the payload caused it. Always capture baseline → exploit → control.
- **Proportional timing for blind/time-based findings** — a single 5s delay can be network jitter. Confirm with SLEEP(0)/SLEEP(3)/SLEEP(7) and show the delay scales with the value, repeated 2-3x.