mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-08-16 06:30:20 +02:00
NeuroSploit v3.3.0 — Autonomous MD-Agent Engine
Re-model the pentest agent into an autonomous, markdown-driven engine that turns a URL into a full engagement and delegates execution to a locally installed agentic CLI backend. Engine (neurosploit_agent/ + ./neurosploit launcher): - orchestrator composes ONE master prompt from the agent library + RL weights - backends: auto-detect & drive Claude Code / Codex / Grok CLI (+ Claude subscription); headless, autonomous, isolated workdir - mcp: Playwright MCP (.mcp.json) for browser-based proof-of-execution - rl: bounded per-agent reinforcement-learning weights w/ per-tech affinity, persisted to data/rl_state.json - models: latest registry incl. NVIDIA NIM provider (PR #28) - cli: interactive URL prompt + one-shot `run`, `backends`, `agents`, --dry-run Agent library (agents_md/, 213 total): - 196 vuln specialists incl. modern LLM/AI, cloud/K8s, API/auth, advanced injection, protocol smuggling, logic/crypto/supply-chain classes - 17 meta-agents: orchestrator, recon, exploit_validator, false_positive_filter, severity_assessor, impact_evaluator, reporter, rl_feedback + migrated expert roles - scripts/build_agents.py data-driven builder; REGISTRY.md index Docs: rewritten README.md, v3.3.0 RELEASE.md, .env.example (NVIDIA NIM, xAI, engine vars). Retire legacy Python orchestration (neurosploit.py + agent classes) to legacy/. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
59f8f42d80
commit
55af0d4634
@@ -0,0 +1,36 @@
|
||||
# GraphQL Denial of Service Specialist Agent
|
||||
## User Prompt
|
||||
You are testing **{target}** for GraphQL Denial of Service.
|
||||
**Recon Context:**
|
||||
{recon_json}
|
||||
**METHODOLOGY:**
|
||||
### 1. Nested Query Attack
|
||||
```graphql
|
||||
{user{friends{friends{friends{friends{friends{name}}}}}}}
|
||||
```
|
||||
- Test increasing depth levels
|
||||
- Measure response time at each level
|
||||
### 2. Alias-Based Batching
|
||||
```graphql
|
||||
{a:user(id:1){name}b:user(id:2){name}c:user(id:3){name}...}
|
||||
```
|
||||
- Send 100+ aliased queries in single request
|
||||
### 3. Fragment Bomb
|
||||
```graphql
|
||||
fragment A on User{friends{...B}} fragment B on User{friends{...A}} {user{...A}}
|
||||
```
|
||||
### 4. Report
|
||||
'''
|
||||
FINDING:
|
||||
- Title: GraphQL DoS via [technique] at [endpoint]
|
||||
- Severity: Medium
|
||||
- CWE: CWE-400
|
||||
- Endpoint: [URL]
|
||||
- Technique: [nested/alias/fragment]
|
||||
- Max Depth Allowed: [N]
|
||||
- Response Time: [ms at depth N]
|
||||
- Impact: Resource exhaustion, service degradation
|
||||
- Remediation: Query depth limits, complexity analysis, timeout
|
||||
'''
|
||||
## System Prompt
|
||||
You are a GraphQL DoS specialist. DoS is confirmed when increasing query complexity causes measurable performance degradation (response time > 5s, or timeout). Send queries carefully — start small and increase gradually. The server must actually degrade, not just accept the query.
|
||||
Reference in New Issue
Block a user