RedAmon HackLab

Two evaluation scenarios. One target. Zero hand-holding.

The HackLab is a deliberately vulnerable environment used to evaluate RedAmon's AI agent end-to-end. The agent receives no credentials and no insider knowledge -- it must gain initial access on its own through info disclosure, JWT forgery, brute force, direct database access, or any other technique it discovers.

All sessions run on a deliberately vulnerable application (DVWS-Node) deployed on our own controlled server for educational and research purposes only. Never use these techniques on systems you do not own or have explicit written authorization to test. Unauthorized access is illegal.

Two Scenarios

The lab supports two different evaluation styles, each answering a different question.

The same target environment is used for both -- only the prompt and the win condition differ.

Target Service Map

Prerequisites (both scenarios)

1. DVWS-Node + CVE Lab deployed on your EC2 instance
2. Full recon pipeline executed and stored in the graph database
3. RedAmon agent configured with the target project

The full target overview, recon data, and all prompts are in REDAMON.HACKLAB.md.

Scenario 1 -- HackLab Prompts

Each prompt points the agent at a specific port and service with no credentials or insider knowledge, then lets it figure out the rest: initial access, endpoint discovery, vulnerability identification, exploitation, and post-exploitation. The agent queries the recon graph for context, selects its own tools, and adapts when things don't go as expected.

Each session includes:

• XXX-XXXXX_session.md -- the raw unedited agent session log (every tool call, response, and reasoning step)
• XXX-XXXXX_sess_decoded.md -- a human-readable walkthrough explaining the full attack chain, key decisions, and what capabilities the agent demonstrated

MISLEADING INTEL (MSL)

Prompts that intentionally give the agent wrong assumptions. The agent must recognize the mismatch, pivot, and still achieve the objective.

NoSQL INJECTION (NQL)

OS COMMAND INJECTION & RCE (RCE)

XXE INJECTION (XXE)

SSRF (SRF)

BROWSER-BASED ATTACKS -- Playwright (BRW)

Prompts that require the Playwright headless browser tool. The agent uses a real Chromium browser to render JavaScript, interact with forms, and test client-side vulnerabilities that curl cannot reach.

Scenario 2 -- CTF Challenges

Status: placeholder. Real challenges are in development.

CTF challenges collapse evaluation to a single binary question: did the agent retrieve the planted flag? Each challenge ships with:

• A goal-only prompt (target + RoE + flag format -- no vulnerability hints, no endpoint hints)
• A planted flag (FLAG{...}) injected into the lab at deployment time
• An automatic grader (substring match against the agent's final output)

Unlike Scenario 1, CTF prompts deliberately withhold the vulnerability class and endpoint. The agent must do its own discovery, classification, and exploitation -- closer to a real bug-bounty or black-box pentest engagement.

Planned Challenges

Each CTF entry will eventually expose:

• prompt -- the goal-only instruction handed to the agent
• flag -- the planted string the grader looks for
• integration -- where in the lab the flag is planted (file path, env var, DB row, etc.)
• roe -- run-specific rules of engagement (e.g. "no external callbacks", "no metadata service")
• session -- decoded walkthrough once a model has solved it

Community Sessions

Share your own RedAmon agent sessions from your real targets and environments. These are not from the HackLab prompt list -- they are real-world pentests, CTFs, or custom lab setups where the agent was used autonomously.

How to Submit

1. Run the RedAmon agent against your own target (your lab, CTF, authorized pentest)
2. Export the session log (saved automatically as .md)
3. Open a PR on the redamon repo:
   • Add your session file to redamon.wiki/hacklab/community/
   • Name it descriptively: your-target_vuln-type_session.md
   • Include a brief summary in the PR description

What to Include in Your PR

## Community Session

**Target:** Brief description (e.g. "HackTheBox - Keeper", "My company's staging API", "Custom CTF lab")
**AI Model:** claude-opus-4-6 / claude-sonnet-4-6 / other
**Attack type:** What the agent was asked to do
**Outcome:** What it achieved
**Total time:** Xm
**Interesting because:** Why this session is worth sharing (unexpected pivot, creative chain, edge case, etc.)
**YouTube:** https://youtu.be/your-video-id

Guidelines

• Authorized targets only -- do not submit sessions from unauthorized testing
• Redact sensitive data -- remove real IPs, domains, credentials, or client info before submitting
• YouTube video required -- record your screen while the agent runs and upload to YouTube
• Failed sessions welcome -- if the agent got stuck or took a wrong path, that's valuable feedback
• Different models encouraged -- comparing opus vs sonnet on the same target helps everyone