Challenge
- Category: Warmups (Day 01), 2 points (Single Solve)
- Game Master ID:
warmups-day-01 - Prompt:
Everyone has to start somewhere. I hear sixty-four is a good base.
You can download the single-solve file for this challenge here: a_little_based.txt (148 B) or ask the Game Master for your single-solve file in the AI Homebase virtual machine.
- Game Master question: "Decode the assigned blob completely. What exact answer slug does its final non-empty decoded line instruct you to submit?" (answer field
message)
Artifacts
| File | Source | SHA-256 |
|---|---|---|
a_little_based.txt | CourseStack download link | 18a470c3708678d69c1fb0a39e6b94b875b07e323f5f104c1662179c2f9632fa |
blob.txt | Game Master, assigned to this attempt | 939968bee79630a691e906f1e1a9f6af1d286a34ee8eae23d7a9485e519aa4cd |
Triage
FAST PATH. "Sixty-four is a good base" -> Base64.
Investigation
- I decoded the CourseStack download with one Base64 pass:
Nice work decoding this warmup! To solve, submit this exact answer to the Game Master: dashing-tent-mosaic-17 - I submitted
dashing-tent-mosaic-17to the Game Master, which answered{"result":"incorrect"}. This file did not match the artifact assigned to the attempt. - The Game Master start response named a different artifact,
blob.txt, with SHA-256939968be.... Downloaded through the Homebase proxy (http://[ip]/huntress-ctf-proxy), it contained:ZmxhZ3thODY2MjYxNWMyOGRiZmZhNTgzM2NkNzQxNGJjNTRjY30= - One Base64 decode gave plaintext:
- Decodedflag{a8662615c28dbffa5833cd7414bc54cc}
- I submitted it under
message, and the Game Master answered{"result":"CORRECT","name":"A Little Based",...}.
Flag Recovery
- Source: the assigned
blob.txt. Its hash matches the one in the Game Master start response. - Transform: a single Base64 decode.
- Verification: decoding locally gives the same plaintext, and the blob hash matches. The Game Master returned
CORRECT.
Flag
- Decodedflag{a8662615c28dbffa5833cd7414bc54cc}
Time Trial and Mastery
The Homebase agent ran both from a script (a_little_based_run.py, saved in the Homebase workspace [local path], not copied here). It used one HTTP session and no hand steps.
- Mastery (
warmups-day-01/mastery) is locked until the Time Trial is done. Starting it first returns HTTP 409prerequisite_required. - Time Trial: start returns
attempt_id,download(a capability URL),sha256,answer_ids:["message"]and a serverdeadlineof start+30s. The script downloads, Base64-decodes and submits. Result:CORRECTin 1.363 s. That beat the server deadline but missed the 1 s stated on CourseStack. - Mastery: three artifacts (
blob-01..03.txt), each with its own capability URL and SHA-256 in the start response, downloaded concurrently. Each blob starts with a numeric index and a tab before the Base64 payload, so strip that prefix before decoding. Answers go underset1.message,set2.messageandset3.message. Result:CORRECTin 2.937 s.
| Mode | Answer(s) the Game Master marked CORRECT |
|---|---|
| Time Trial | Decodedflag{8b388c5593234cb644f27d67bcfc580c} |
| Mastery set1 | Decodedflag{dbc41d0e7827589462c583c56172b001} |
| Mastery set2 | Decodedflag{21ae3a17e5ccc787d0ccd2ada39fcf81} |
| Mastery set3 | Decodedflag{8b422c104b592939505f36b58dbe70ae} |
Verification: these are the Game Master's own CORRECT responses as relayed by the Homebase agent. The dynamic artifacts were not copied locally, so they could not be re-decoded independently.
Minimal Reproduction
# in AI Homebase: fetch the attempt's blob.txt via the Game Master proxy, then
base64 -d blob.txt
Lessons Learned
- The static CourseStack download and the Game Master's assigned artifact can differ. Always solve the artifact named in the Game Master start response, and check its SHA-256. The download's "answer slug" was a decoy for this attempt and was marked incorrect.
- The Game Master's stated answer format ("slug") did not match what it accepted (a
flag{}value). Trust the bytes, not the stated format. - Homebase uses the proxy
http://[ip]/huntress-ctf-proxy(with?op=list, start, and submit operations). The CourseStack proxy URL works only after you click Connect on the challenge page, which issues the auth token.