Tactical LogHuntress CTF 2026 // team archive

Days / Day 01 / Other / Welcome Robots

DAY 01//LANE: OTHER//STATUS: CORRECT x1

Welcome Robots

Other SSTTMM Modes reported CORRECT in this write-up

Challenge

  • Event: Huntress CTF 2026 - Day 1 / welcome lane. Author: John Hammond / Just Hacking Training. Category: AI Native. Mode: Single Solve (untimed). 10 points.
  • Prompt: "Ask your AI teammate to identify the Welcome Robots challenge and provide the answer for the CTF platform." (Launch the AI Homebase VM, Connect to its AI workbench, ask it to find the challenge and return the answer; submit the returned completion code on CourseStack.)

Triage

  • AI-native orientation: the answer is obtained by driving the Homebase AI workbench (reachable only via the CourseStack-authenticated web terminal; the 10.x Game Master and bare proxy deep-links are not reachable from an external box).
  • Game Master proxy: http://[ip]/huntress-ctf-proxy (ops: list/start/status/artifact/submit/retry/openapi; + download and params day/lane/all/search/capability/delivery exposed in openapi).

Investigation

  1. Opened CourseStack (logged in as blandman3) -> Day 01 -> Welcome Robots -> Connect to the Running AI Homebase VM ([ip]) -> AI workbench (GPT-6 Luna).
  2. Asked the workbench the prescribed question. Plain POST {op:start,challenge:welcome-robots} returned {"error":"flag_unavailable", name, prompt, guidance} - no answer_id. status same. openapi showed no special welcome/validate op.
  3. KEY: POST {op:retry,challenge:welcome-robots} returned operation_not_allowed, but the FOLLOW-UP POST {op:start,...} then provisioned the attempt and issued answer_ids:["flag"] with a live issued_flag.
  4. POST {op:submit,challenge:welcome-robots,answers:{flag:"<issued value>"}} returned {"result":"CORRECT",...,"flag":"ee8f5d38939f092186a9da5341d956fb"}. (Empty answers and the literal name both returned "incorrect".)
  5. Entered the completion code in the CourseStack form -> Correct, 10 points.

Flag Recovery

  • The completion code is issued by the live Game Master after a retry-then-start sequence re-provisions the attempt; it is submitted under answer_id flag. Not present in the local AGENTS.md guide.

Flag

  • Tokenee8f5d38939f092186a9da5341d956fb

Minimal Reproduction

From the Homebase workbench, against http://[ip]/huntress-ctf-proxy:

  1. POST {"op":"retry","challenge":"welcome-robots"} (may say operation_not_allowed - that's fine)
  2. POST {"op":"start","challenge":"welcome-robots"} -> note issued_flag and answer_ids:["flag"]
  3. POST {"op":"submit","challenge":"welcome-robots","answers":{"flag":"<issued_flag>"}} -> result:CORRECT returns the completion code
  4. Submit that code on CourseStack.

Lessons Learned

  • When a Game Master start returns flag_unavailable, a retry then start can provision the attempt and issue the flag - don't conclude "no answer available" from the first start.
  • AI-native challenges are solved by driving the Homebase AI workbench through the CourseStack-authenticated web terminal; external SSH/Game-Master access needs the CTF VPN.
  • Always submit under the exact answer_ids the start response gives (here, flag).