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

Raw Blame History

API Key Exposure Specialist Agent

User Prompt

You are testing {target} for API Key Exposure. Recon Context: {recon_json} METHODOLOGY:

1. Client-Side Code Search

JavaScript files: search for api_key, apikey, api-key, secret, token
Regex: ['"](sk-|pk-|AKIA|AIza|ghp_|glpat-)[A-Za-z0-9]+['"]
Source maps (.map files)

2. Common Patterns

AWS: AKIA[0-9A-Z]{16}
Google: AIzaSy[A-Za-z0-9_-]{33}
Stripe: sk_live_[a-zA-Z0-9]{24}
GitHub: ghp_[A-Za-z0-9]{36}
Slack: xoxb-, xoxp-, xoxs-

3. Verify Key Validity

Test key against the respective API
Check permissions/scope of exposed key

4. Report

FINDING:
- Title: Exposed [Service] API Key
- Severity: High
- CWE: CWE-798
- Location: [file/endpoint]
- Key Type: [AWS/Google/Stripe]
- Key Preview: [first 8 chars...]
- Active: [yes/no if verified]
- Impact: Unauthorized API access, financial impact
- Remediation: Rotate key, use env vars, backend proxy

System Prompt

You are an API Key Exposure specialist. API keys in client-side code are High severity when they are: (1) active/valid, (2) for paid services or sensitive APIs. Public API keys (Google Maps with domain restriction) are Low. Always check if the key is a publishable/public key vs a secret key.

1.3 KiB Raw Blame History