PoC-Validator Skill

SkillDatabases & data

Lets your agent generate and test proof-of-concept exploits like SQL injection inside an isolated sandbox.

Available today. Use it from your connected AI after setup.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the PoC-Validator Skill skill

About this skill

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

What this skill tells your AI

The instructions your AI receives, as published by shadd0wtaka/zen-ai-pentest in .agents/skills/poc-validator/SKILL.md and read by ahel’s review.

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

LevelPayload TypeToolsUse Case
0Passive detectionNoneVulnerability confirmation only
1Safe payloadsSQLMap --risk 1Non-destructive testing
2Active exploitationSQLMap --risk 2, MetasploitControlled exploitation
3AggressiveAll tools with full payloadsFull 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:

  1. Validate target is not in private ranges (guardrails/ip_validator.py)
  2. Confirm explicit authorization in database
  3. Set execution timeout
  4. Enable Docker sandbox
  5. Log all actions to audit trail

See references/safety_requirements.md for complete safety checklist.

Error Handling

ErrorCauseSolution
Sandbox timeoutPayload too slowIncrease timeout or use faster technique
Container crashResource exhaustionReduce threads, increase memory limit
Network blockedEgress filteringVerify allowed outbound in config
Verification failedWAF/IPS blockingTry 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

Scripts

  • scripts/payload_generator.py - Generate tailored exploit payloads
  • scripts/sandbox_executor.py - Execute exploits in Docker sandbox
  • scripts/verify_exploit.py - Verify exploitation success
  • scripts/cleanup_sandbox.py - Clean up sandbox resources

Signals

GitHub stars
469
Forks
81
Last commit
Sep 2026

ahel review

  • K1binfo
    installs-packages (in references/docker_sandbox_setup.md)

Automated review, not a security audit. Ruleset v1+k2.

Advanced
Item type
skill
Key
poc-validator
Source
github.com/shadd0wtaka/zen-ai-pentest