mirror of
https://github.com/gadievron/raptor.git
synced 2026-04-24 21:46:00 +03:00
[GH-ISSUE #23] LLM-Driven Exploit Reproduction with Vagrant #1
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/raptor#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Cxnrvd on GitHub (Dec 6, 2025).
Original GitHub issue: https://github.com/gadievron/raptor/issues/23
Originally assigned to: @danielcuthbert on GitHub.
I often find vulnerable endpoints during pentests that have no public exploits. It would be extremely useful if RAPTOR’s /exploit feature could integrate with Vagrant (or similar) to spin up a safe, isolated environment for reproducing these issues.
Idea:
LLM suggests possible exploit vectors based on the endpoint or service.
RAPTOR auto-generates and launches a matching Vagrant environment.
Pentester tests the LLM’s suggestions safely inside that sandbox.
This would bridge analysis → reproducible PoC, especially for custom or undocumented vulnerabilities.
Would love to see this as an optional module or extension.
@danielcuthbert commented on GitHub (Dec 7, 2025):
I like your thinking here. Ill have a sketch as to how this flow might work but good addition.