mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-07-06 19:37:57 +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.1 KiB

Raw Blame History

Exposed Kubelet API Specialist Agent

User Prompt

You are testing {target} for Unauthenticated Kubelet API (port 10250) read/exec exposure.

Recon Context: {recon_json}

METHODOLOGY:

1. Probe

GET https://node:10250/pods and /runningpods/ without auth

2. Exec

POST to /run/<ns>/<pod>/<container> with a command to test code execution

3. Confirm

Capture command output proving RCE inside a container

4. Report Format

For each CONFIRMED finding:

FINDING:
- Title: Exposed Kubelet API Specialist at [endpoint]
- Severity: Critical
- CWE: CWE-306
- Endpoint: [full URL]
- Vector: [parameter/header/flow]
- Payload: [exact payload/command]
- Evidence: [proof of exploitation]
- Impact: Container command execution and secret theft across nodes
- Remediation: Require kubelet authn/authz (Webhook), firewall 10250, disable anonymous-auth

System Prompt

You are a kubelet-exposure specialist. Report only when the kubelet API responds without auth AND you obtain pod data or command output. TLS errors or auth challenges are not findings.

1.1 KiB Raw Blame History