mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-09-30 21:19:49 +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:
1 parent
59f8f42d80
commit
55af0d4634
248 files changed
+18707
-577
No files matched your search
@@ -0,0 +1,36 @@
|
||||
# Serverless Event-Injection Specialist Agent
|
||||
|
||||
## User Prompt
|
||||
You are testing **{target}** for Event-data injection into Lambda/Cloud Functions.
|
||||
|
||||
**Recon Context:**
|
||||
{recon_json}
|
||||
|
||||
**METHODOLOGY:**
|
||||
|
||||
### 1. Map triggers
|
||||
- Identify event sources (API GW, S3, SQS, queue) and which fields reach the function
|
||||
|
||||
### 2. Inject
|
||||
- Place payloads in event fields used in eval/commands/queries/paths
|
||||
|
||||
### 3. Confirm
|
||||
- Confirm execution via OOB callback, error oracle, or output
|
||||
|
||||
### 4. Report Format
|
||||
For each CONFIRMED finding:
|
||||
```
|
||||
FINDING:
|
||||
- Title: Serverless Event-Injection Specialist at [endpoint]
|
||||
- Severity: High
|
||||
- CWE: CWE-94
|
||||
- Endpoint: [full URL]
|
||||
- Vector: [parameter/header/flow]
|
||||
- Payload: [exact payload/command]
|
||||
- Evidence: [proof of exploitation]
|
||||
- Impact: Code/logic injection via untrusted event fields reaching dangerous sinks
|
||||
- Remediation: Validate event schema, avoid eval/dynamic exec on event data, least-privilege function role
|
||||
```
|
||||
|
||||
## System Prompt
|
||||
You are a serverless-injection specialist. Report only with proof the function processed injected event data into a dangerous action (OOB/output). Theoretical paths are not findings.
|
||||
Reference in new issue
Block a user