vuln-hunter

Identify security weaknesses in a paused debuggee via import/export reconnaissance and PoC testing.

196|17|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/dariushoule/x64dbg-skills --skill vuln-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vuln-hunter
Source: https://github.com/dariushoule/x64dbg-skills/tree/main/skills/vuln-hunter
Command: npx skills add https://github.com/dariushoule/x64dbg-skills --skill vuln-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hunts for vulnerabilities in a running debuggee by systematically analyzing imports/exports, mapping attack surfaces, and iteratively testing with PoC generation to validate bugs in the target process.

Core Features & Use Cases

  • Reconnaissance of imports/exports to identify external entry points and potential sinks
  • Attack-surface triage with function labeling, context assessment, and risk ranking
  • Guided bug-hunting loop with instrumentation, breakpoints, and trace-based analysis
  • PoC generation and evidence collection to demonstrate impact and reproducibility

Quick Start

Pause the target in x64dbg and run the vuln-hunter workflow to start reconnaissance and iterative bug testing.

Frequently Asked Questions about vuln-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find vulnerabilities in a running debuggee using x64dbg?

Attack-surface triage involves labeling functions, assessing execution context, and ranking risk-prone paths within the target process. This structured triage helps prioritize vulnerable entry points and I/O sinks for focused vulnerability investigation.

What is the best way to validate a vulnerability PoC during live debugging?

Before starting reconnaissance, you must have the target process running and paused in a compatible debugger like x64dbg. Pausing the debuggee is required to safely perform import and export analysis and map the active attack surface.

Can I use this approach to analyze imports and exports for security sinks?

Yes, you can analyze imports and exports to identify external entry points and potential security sinks. This reconnaissance maps I/O sinks and labels risk-prone paths to guide focused investigation during the debugging session.

Why do I need to pause the target process before starting vulnerability reconnaissance?

Pausing the target process in the debugger ensures memory and execution states remain stable. This allows accurate import and export reconnaissance, function labeling, and safe instrumentation for PoC-based testing.