Tactical LogHuntress CTF 2026 // team archive

Days / Day 27 / Mobile Android / Dependency Surface

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

Dependency Surface

Mobile Android SSTTMM Modes reported CORRECT in this write-up

Dependency Surface (mobile-android, Day 27)

Prompt: prove which generated dependency flaw is reachable from an exported mobile surface.

Method: the artifact is an Android APK. The framework's mobile solver (autosolve_mobile via agent_solve_cid.py, per-CID working copy in scripts/solve.py) decoded the answers statically from the APK, including a secondary DEX for the dynamic codec. Codecs seen: base64, caesar, hex, reverse, split, xor. The APK was not executed. Single had 1 answer; Time Trial and Mastery each re-derived their answers from that attempt's own bytes (Mastery had 11 answers).

Results (all GM-accepted, solved by Blandman3):

  • Single: 9a72888b7ca5f9cfc1ccd0eef6e4dd81
  • Time Trial: 07804559eeeec1976ba264dfd54ec322
  • Mastery: b0fc41f06bb5b5b1139593f942304496

Notes:

  • First run held Time Trial because challenges/_lib/prebrief.py had a SyntaxError (shared lib, fixed by someone else); no window was opened or spent. Rerun after the fix completed Time Trial and Mastery.
  • The framework opened the Time Trial and Mastery modes as RANKED (run_for_time) attempts on this rerun, which CLAUDE.md says should not happen under the 2026-10-11 policy. The agent did not request that; flagged for the Commander.