The repository has now crossed 1,700+ Docker pulls, and the GitHub traffic is showing something even more interesting: people are cloning the project, exploring the code, and going deeper than the README.

So let me answer the question I keep getting:

What can HunterX actually investigate?

HunterX currently covers a broad vulnerability surface through its proof-contract registry:

• SQL Injection
• NoSQL Injection
• XSS
• SSRF
• Path Traversal / LFI
• RCE / Command Injection Indicators
• IDOR / BOLA
• SSTI
• XXE
• Authentication
• Authorization
• API
• GraphQL
• Open Redirect
• CORS
• Sensitive Information Exposure
• Security Misconfiguration
• Known Vulnerable Components
• Dependency Vulnerabilities
• Cloud Exposure
• UNKNOWN_BEHAVIOR

And there is an important distinction here.

HunterX is not saying that every vulnerability class has identical validation depth.

It doesn't.

The validation depth is defined by the individual proof contract.

That's intentional.

Because finding:

"Possible SQL Injection"

isn't the same thing as proving:

"This parameter is injectable, here is the evidence, here is how it was verified, here is the reproducible path, and here is the PoC."

That's the direction HunterX is built around.

How does that compare to the usual toolkit?

Nuclei is phenomenal for template-driven detection.

Nmap is phenomenal for network/service discovery.

Burp Suite is phenomenal for interactive web testing.

SQLmap is extremely mature for SQL injection exploitation.

OWASP ZAP provides a powerful proxy/scanning platform.

FFUF is excellent for fuzzing and content discovery.

I'm not trying to pretend those tools don't exist.

The interesting part is what happens when you need to move between them.

HunterX is designed around a different workflow:

Observe → Hypothesize → Probe → Verify → Produce Evidence

Instead of stopping at a detection signal, the goal is to move toward a validated finding.

That's the part I'm building.

Not another tool that gives you 400 alerts.

A system that tries to answer:

"Can we actually prove this?"

And yes — HunterX can work alongside the tools researchers already use.

The goal isn't to replace the entire security ecosystem.

The goal is to orchestrate it, reason over its output, and push findings toward validation and proof.

If you're into offensive security, bug bounty, pentesting, vulnerability research, or security automation:

Try HunterX.

Break it.

Test it.

Find something it misses.

Tell me where the reasoning fails.

That's how this project gets better.

And if you think the idea is worth watching, ⭐ Star the repository.

It genuinely helps the project reach more security researchers.

🔗 https://github.com/nullc0d30/HunterX

HunterX — Don't just detect. Investigate. Validate. Prove.