Skip to main content

Overview

RAPTOR provides truly autonomous security analysis powered by Large Language Models (LLMs). The system analyzes vulnerabilities with deep context awareness, including dataflow paths, sanitizer effectiveness, and exploitability assessment - with no templates.
This is autonomous analysis - the LLM makes real security engineering decisions based on actual code, not pattern matching.

Key Features

  • LLM-Powered Analysis: Claude, GPT-4, or local models (Ollama/DeepSeek/Qwen)
  • Dataflow Path Validation: Tracks tainted data from source to sink
  • Sanitizer Bypass Detection: Identifies ineffective or bypassable mitigations
  • Exploitability Scoring: Rates vulnerability severity and feasibility
  • Cost Tracking: Built-in budget management for API usage
  • Automatic Fallback: Gracefully handles model failures

Analysis Workflow

The autonomous agent follows this workflow:

1. Context Extraction

The agent automatically extracts full context for each vulnerability:

2. Dataflow Path Analysis

For vulnerabilities with dataflow paths, the agent traces data from source to sink:

3. Deep Validation

The LLM performs rigorous validation to separate real vulnerabilities from false positives:
1

Source Control Analysis

Is the data actually attacker-controlled?
  • HTTP request, user input, file upload → Attacker controlled
  • Config file, environment variable → Requires access first ⚠️
  • Hardcoded constant, internal variable → False positive
2

Sanitizer Effectiveness

Can the sanitizers be bypassed?
  • Analyze what each sanitizer actually does
  • Check for encoding bypasses (URL encoding, double encoding)
  • Verify coverage across all code paths
3

Reachability Analysis

Can an attacker trigger this code path?
  • Check for authentication/authorization barriers
  • Identify prerequisites that block exploitation
  • Verify the code is used in production
4

Exploitability Assessment

What’s the actual risk?
  • Determine attack complexity (low/medium/high)
  • Identify required primitives and prerequisites
  • Estimate CVSS score (0.0-10.0)

LLM Provider Support

Claude Sonnet 4.5 provides the best exploit generation quality and security analysis depth.
Cost: ~0.003per1Kinputtokens,0.003 per 1K input tokens, 0.015 per 1K output tokens

OpenAI GPT-4

Cost: ~$0.01 per 1K tokens

Ollama (Local/Free)

Important Limitations:
  • Vulnerability analysis and patching: Works well with Ollama models
  • Exploit generation: Requires frontier models (Claude/GPT-4)
  • Ollama models may generate invalid/non-compilable exploit code
For production-quality exploits, use Claude or GPT-4.
Supported Ollama Models:
  • deepseek-coder:33b - Best for code analysis
  • qwen2.5-coder:32b - Strong at security tasks
  • codellama:70b - Meta’s code model

Configuration

LLM Config

The LLM client automatically handles model selection, fallback, and retry:

Cost Tracking

Built-in cost tracking for budget management:

Analysis Output

Structured Analysis

The LLM returns structured analysis with confidence scores:

Output Files

The agent saves detailed results:

Budget Management

Setting Budget Limits

LLM API calls can become expensive at scale. Set budgets to avoid surprises.

Cost Estimates

Per Vulnerability Analysis:
  • Context extraction: ~2K tokens
  • Deep validation: ~4K tokens
  • Exploit generation: ~6K tokens
  • Patch generation: ~4K tokens
Total per finding: 16K tokens ($0.24 with Claude) For 100 findings: ~$24

Best Practices

Scanners with dataflow support (CodeQL, Semgrep) provide much better context:
  • Source/sink tracking
  • Sanitizer detection
  • Intermediate transformation steps
This enables the LLM to make better validation decisions.
Start with high-severity findings to maximize ROI:
The LLM is very good but not infallible:
  • Check false positive determinations
  • Verify exploitability assessments
  • Review generated exploit code
  • Test patches before deploying
Local models work well for analysis but struggle with exploit generation:
  • Analysis/patching: Ollama is fine
  • Exploit generation: Use Claude or GPT-4
  • Critical findings: Always use frontier models

Example: End-to-End Analysis

See Also

Exploit Generation

Generate working exploit PoCs

Patch Creation

Create secure patches

Crash Analysis

Analyze binary crashes