DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to hunt exploitable flaws in your own codebase with Vuln Hunter

Run the attacker-first scanner to get verified issues, each with an executable exploit and a proposed fix.

Authorization notice. Vuln Hunter is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. The installer runs from a cloned repo, so read install.sh before you execute it on a machine that holds code you care about.

Who it is forAn application security engineer preparing a release of a service they own, who wants findings that are proven exploitable rather than pattern matches.

The problemTraditional scanners flag suspicious code patterns and produce many false positives, so teams spend time triaging issues that cannot be exploited.

The outcomeA short list of verified issues, each with an executable exploit and a proposed fix, after falsification filtering removes unsupported findings.

What you need first

  • Source code you own or are authorized to audit
  • Your own model access, using the most capable reasoning model your agent harness offers
  • An agent harness with a skills directory and subagent support
  • Python and git installed locally

Steps

  1. Clone the repository with git clone https://github.com/nealbridges/VulnHunter (inferred, check the README)
  2. Run the installer from the repo folder with bash install.sh, setting VULNHUNT_SKILLS_DIR for your harness first if it does not use a default location (inferred, check the README)
  3. Open your agent harness in the folder of the code you own and are authorized to audit
  4. Run /vulnhunt to start the hunt from entry points toward dangerous sinks
  5. Review each confirmed finding, its exploit, and its proposed fix before acting on it

Prompt for your agent

Using the VulnHunter repo at nealbridges/VulnHunter, run the /vulnhunt skill against <target repo path>, which I am authorized to audit. Return a list of confirmed findings with each finding's entry point, sink, and exploit status. Verify that every listed finding includes an executable exploit or is labeled as lacking one.

Caveat. Exploit execution is described as ideal rather than guaranteed, and the Docker-first sandbox for exploit validation is still in progress in this fork.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page