One run from start to finish. A brief becomes a plan, recon maps the target, the agents propose candidates, and the proof engine drops every candidate it cannot prove.
Features
- Every ounce out of your model. A supervisor splits the work across specialist agents armed with attack skills. A second model reviews the plan and calls out what it missed.
- Any starting point. A URL, an IP range, a domain, a repo, an app bundle, an API spec or a whole bug-bounty scope document. One command takes all of them.
- Brief it in plain English.
-p "focus on IDOR and broken access control"and the run aims there.--dry-runshows which words set which flag. - Re-proved, not guessed. Deterministic code with no AI in it re-tests every candidate. An agent can never mark its own finding confirmed.
- Chains bugs, chases impact. Gimorra combines findings into larger attacks, then follows a confirmed bug to see what else it hands an attacker.
- Hunts what scanners miss. The hypothesis phase assumes a critical bug exists and goes looking for it, long after an ordinary pass would give up.
- Logged in like a real user. Hand it accounts and it logs in as each one before the attack. Access-control bugs between users are fair game.
- Source and live, together. Pass
--sourceand the run audits the code while it attacks the app. Every agent can read the source. - Evidence you can replay. A hash-chained trail ties each finding to the exact request and response that proved it, with copy-paste
curlsteps. - Memory between runs. The next engagement starts from what the last one learned: pages, endpoints, working techniques and held accounts.
- Bring your own model. A Claude login, an Anthropic key, a proxy or any OpenAI-compatible endpoint. Route the supervisor and the children to different models.
- Built for CI and long runs.
--exit-on-findingsfails the build.--detachsurvives a closed terminal.--resumepicks up where a run stopped, without paying twice.
Inside the console
Everything a run does lands in the console, live while it runs and frozen when it finishes. These screenshots come straight from the demo console.
The Gimorra console. Every engagement, every finding, every dollar spent, on one screen.

Engagement report: proven versus recorded, by severity and by class

Finding detail: the proof verdict and the requests that reproduce it

Agent jobs: the supervisor, its specialists, and what each one cost

Attack surface: every host, service, endpoint and parameter, scope-checked

Coverage: which technique ran where, and what the run never answered

Engagements: every run, its phase, findings and surface at a glance
What a run does
One command runs a whole engagement through a fixed order of phases. The console prints one line per phase, marked with its symbol.⌥ Resolve, ◎ target and ◈ scope
⊙ Crawl
⌖ Observe
⋆ Ideate
❖ Attack
⊢ Proof
Closing phases
- ⊔ Salvage recovers results from child agents that stopped before they wrote them.
- ≟ Hypothesis assumes a high or critical bug exists and hunts for it.
- ⊨ Triage settles what the proof engine left open: repair the candidate or mark it a false positive.
- ⋈ Compose chains findings into a larger attack.
- ⊩ Exploit follows one confirmed finding to see what else it gives an attacker.
✎ Elaborate, ⊕ surface and ≡ done
--skip <phase>, for example --skip hypothesis. Running a scan covers the rest of the flags.
Safety controls in code
Gimorra doesn’t ask you to click “approve” on every action. Its guardrails live in code, so you set the level of supervision once per run and let it work.The proof engine decides
Cleanup and a kill switch
Scope guard on every tool call
What you can give it
--intensity sets how hard the run hits, from passive to aggressive. Nothing else needs tuning to get a first result.
Vigolium or Gimorra
Vigolium · Free and open source
- 215+ scanner modules in one binary
- Native speed on every push, agentic depth before every release
- Runs on your own infrastructure, in your own CI
Gimorra · Proprietary, by request
- Squeezes every ounce of intelligence out of the model you bring
- Any starting point: URL, IP range, repo or app bundle
- Every candidate re-proved before it counts as confirmed
Next steps
Installation
LLM configuration
Running a scan
See what Gimorra finds before you commit: open the demo console, then email [email protected] to put it on your own target.
