poc-validator
Skill470 starsChanged 4 months agoMITView on GitHub
Proof-of-Concept (PoC) Validation Skill for security exploit verification. Use when validating exploitability of vulnerabilities, generating tailored payloads, executing exploits in sandboxed environments, or verifying successful exploitation (e.g., SQL injection, CVE exploitation, command injection). Triggers on tasks involving payload generation, exploit execution verification, sandboxed testing, or confirmation of administrative access/data exfiltration after exploitation attempts.
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
Use scripts/sandbox_executor.py for isolated exploit testing:
- Distinctive: line 58
Read-only filesystem with tmpfs for output
- Distinctive: line 61
Critical: All exploit execution MUST use sandbox.
- Very specific: line 65
Use scripts/verify_exploit.py to confirm exploitation:
- Distinctive: line 67
RCE: Verify command output in response
- Distinctive: line 70
File Upload: Verify file presence/execution
- Distinctive: line 103
Before any exploit execution:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PoC-Validator Skill
Validates vulnerability exploitability through controlled payload generation, sandboxed execution, and success verification.
Quick Start
Generate and validate a PoC for SQL injection:
from scripts.payload_generator import PayloadGenerator
from scripts.sandbox_executor import SandboxExecutor
from scripts.verify_exploit import ExploitVerifier
# Generate payload
gen = PayloadGenerator()
payload = gen.generate_sql_payload(
target_url="http://target.com/login",
parameter="username",
technique="error_based"
)
# Execute in sandbox
executor = SandboxExecutor()
result = await executor.execute_sqlmap(
target="http://target.com/login",
payload=payload,
risk_level=2
)
# Verify success
verifier = ExploitVerifier()
is_exploitable = await verifier.verify_sql_injection(result)Workflow
1. Payload Generation
Use scripts/payload_generator.py for:
- CVE-based exploits: Lookup known payloads from vulnerability_mapping.json
- SQL Injection: Error-based, Union-based, Time-based, Boolean-based
- Command Injection: System command payloads with evasion techniques
- Path Traversal: Directory traversal sequences
- XXE/XML Injection: External entity payloads
See references/payload_patterns.md for complete payload library.
2. Sandbox Execution
Use scripts/sandbox_executor.py for isolated exploit testing:
- Docker container isolation with resource limits
- Network isolation (no egress to private ranges)
- Execution timeouts (default: 300s)
- Read-only filesystem with tmpfs for output
- Automatic cleanup post-execution
Critical: All exploit execution MUST use sandbox. Never run exploits directly on host.
3. Success Verification
Use scripts/verify_exploit.py to confirm exploitation:
- SQL Injection: Detect database version extraction, table enumeration
- RCE: Verify command output in response
- Auth Bypass: Confirm session token/admin access
- Data Exfiltration: Detect sensitive data patterns in responses
- File Upload: Verify file presence/execution
Risk Levels
| Level | Payload Type | Tools | Use Case |
| 0 | Passive detection | None | Vulnerability confirmation only |
| 1 | Safe payloads | SQLMap --risk 1 | Non-destructive testing |
| 2 | Active exploitation | SQLMap --risk 2, Metasploit | Controlled exploitation |
| 3 | Aggressive | All tools with full payloads | Full PoC validation |
Integration with Zen-AI-Pentest
# Integration with ExploitAgent
from autonomous.exploit_validator import ExploitValidator
def validate_poc(self, vulnerability: dict) -> dict:
"""Validate vulnerability with PoC execution."""
validator = ExploitValidator(
sandbox_enabled=True,
risk_level=vulnerability.get("risk", 1)
)
return validator.validate(
vuln_type=vulnerability["type"],
target=vulnerability["target"],
evidence=vulnerability["evidence"]
)Safety Controls
Before any exploit execution:
- Validate target is not in private ranges (guardrails/ip_validator.py)
- Confirm explicit authorization in database
- Set execution timeout
- Enable Docker sandbox
- Log all actions to audit trail
See references/safety_requirements.md for complete safety checklist.
Error Handling
| Error | Cause | Solution |
| Sandbox timeout | Payload too slow | Increase timeout or use faster technique |
| Container crash | Resource exhaustion | Reduce threads, increase memory limit |
| Network blocked | Egress filtering | Verify allowed outbound in config |
| Verification failed | WAF/IPS blocking | Try evasion techniques from payload_patterns.md |
Output Format
{
"poc_id": "uuid",
"vulnerability_id": "vuln-123",
"status": "verified|failed|inconclusive",
"exploit_type": "sql_injection|rce|xxe|...",
"payload_used": "...",
"sandbox_logs": "...",
"evidence": {
"before": "...",
"after": "...",
"extracted_data": "..."
},
"risk_level": 2,
"timestamp": "2026-03-20T14:46:00Z",
"verified_by": "exploit_agent_v3"
}References
- Payload Patterns Library - Complete payload collection
- Sandbox Setup Guide - Docker configuration details
- Safety Requirements - Mandatory safety checks
- CVE Database Schema - CVE lookup structure
Scripts
scripts/payload_generator.py- Generate tailored exploit payloadsscripts/sandbox_executor.py- Execute exploits in Docker sandboxscripts/verify_exploit.py- Verify exploitation successscripts/cleanup_sandbox.py- Clean up sandbox resources
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- autonomous/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- workflow-orchestratorSkill
- research-orchestratorSkill
- tdd-agentSkill
- ai-delegationSkill
- bash-automationSkill
- browser-automationSkill
- devops-cicdSkill
- devops-dockerSkill
- module-api-scannerSkill
- module-auth-bypass-moduleSkill
- module-beyondtrust-exploitSkill
- module-cert-transparencySkill
- module-cloud-scannerSkill
- module-command-injection-moduleSkill
- module-cve-databaseSkill
- module-cve-updaterSkill
- module-deserialization-moduleSkill
- module-dns-enumSkill
- module-email-harvesterSkill
- module-enhanced-reconSkill
- module-exploit-assistSkill
- module-ivanti-epmm-exploitSkill
- module-metadata-extractorSkill
- module-metasploit-integrationSkill
- module-nuclei-integrationSkill
- module-osintSkill
- module-osint-superSkill
- module-path-traversal-moduleSkill
- module-reconSkill
- module-report-exportSkill
- module-report-generatorSkill
- module-risk-scoringSkill
- module-searchsploit-integrationSkill
- module-service-vulnerability-mapperSkill
- module-siem-integrationSkill
- module-sql-injection-dbSkill
- module-sql-injection-moduleSkill
- module-ssrf-moduleSkill
- module-subdomain-scanner-advancedSkill
- module-subdomain-scannerSkill
- module-super-scannerSkill
- module-vuln-scannerSkill
- module-web-scraperSkill
- module-whois-lookupSkill
- module-windows-shell-bypassSkill
- module-wordlist-generatorSkill
- module-xss-moduleSkill
- module-xxe-moduleSkill
- module-zap-automationSkill
- module-zap-orchestratorSkill
- multi-languageSkill
- rag-vectorSkill
- security-reviewSkill
- .skillsSkill
- tool-aircrackSkill
- tool-amassSkill
- tool-bloodhoundSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

