Tactical LogHuntress CTF 2026 // team archive

Days / Day 19 / Mobile Android / Reflection Maze

DAY 19//LANE: MOBILE ANDROID//STATUS: CORRECT x3

Reflection Maze

Mobile Android SSTTMM Modes reported CORRECT in this write-up

Reflection Maze (mobile-android-day-19-reflection-maze) - Day 19

Lane: mobile-android. Case MOB-19-98E3A78C44, package com.huntress.mobile.d19.v98e3a78c44d6.

Result

All three modes CORRECT via AUTOSOLVE (autosolve_mobile.py), no code change needed:

  • Single Solve: CORRECT in 1.3 s
  • Time Trial: CORRECT in 3.7 s
  • Mastery: CORRECT in 4.3 s (ranked)

Method

  1. artifact_0.bin is an APK (6 members: AndroidManifest.xml, classes.dex, assets/huntress_puzzle.json, META-INF signature files).
  2. assets/huntress_puzzle.json = {"schema":"huntress.mobile.puzzle.v1","day":19,"codec":"reflection","data":"AnswerANS-DFCDF6E9F6ABE632"}.
  3. The "reflection" codec (theme: reflective dispatch over generated equivalent call graphs) is cosmetic: the data field already holds the ANS- plus 16 uppercase hex answer, so the adapter returns it as-is (plain-style). Submitted under answer_id answer, exact normalization.
  4. Single answer: AnswerANS-DFCDF6E9F6ABE632 (accepted). Time Trial and Mastery APKs are mutated per attempt; the same adapter derives each answer from that attempt's own bytes.

Notes

  • The Android topic (reflection / call graphs) is flavour; the puzzle asset's codec decides the answer.
  • Codec "reflection" is new by name but behaves like an earlier plain/passthrough codec; the adapter covered it at first contact.