Tactical LogHuntress CTF 2026 // team archive

Days / Day 26 / Mobile Android / Split Decision

DAY 26//LANE: MOBILE ANDROID//STATUS: CORRECT x1

Split Decision

Mobile Android SSTTMM Modes reported CORRECT in this write-up

Day 26 - Split Decision (Mobile Android)

  • GM challenge id: mobile-android-day-26-split-decision
  • Lane: mobile-android (agent-5), WORKSTATION
  • Modes: Single Solve, Time Trial, Mastery
  • Answer id: answer
  • Answer format: ANS- followed by exactly 16 uppercase hexadecimal characters
  • Single Solve answer (verified live CORRECT): AnswerANS-7E37D134754DEA01
  • Single Solve GM completion token: Token19d2580b87184cc684c574a5abfc9b9f (solved_by Blandman3)

Challenge nature

The artifact is an Android App Bundle delivered as a .apks container (an outer ZIP, magic PK\x03\x04) that holds two split APKs:

  • base.apk (challenge artifact, not published) - the base split
  • feature.apk (challenge artifact, not published) - a configuration / feature split

The puzzle premise ("Reassemble evidence distributed across base and configuration splits") is literal: the answer code is cut into fragments and the fragments are scattered across the two splits. No single file contains the whole answer.

Container / member map (from the real bytes):

outer .apks (PK, 21536 bytes)
  base.apk    (12704)
    AndroidManifest.xml
    assets/huntress_puzzle.json      <- base split skeleton (119 bytes)
    classes.dex
    META-INF/FIXTURE-.{SF,RSA}, MANIFEST.MF
  feature.apk (8552)
    AndroidManifest.xml
    assets/huntress_feature.json     <- one fragment (86 bytes)
    META-INF/FIXTURE-.{SF,RSA}, MANIFEST.MF

How the split codec works

base.apk -> assets/huntress_puzzle.json:

{"schema": "huntress.mobile.puzzle.v1", "day": 26, "codec": "split",
 "data": "", "parts": ["", "ANS-7", "E37D13"], "order": [2, 0, 1]}

feature.apk -> assets/huntress_feature.json:

{"codec": "split", "day": 26, "feature": "arena_feature",
 "part": "4754DEA01", "part_index": 0}
  • The base split carries the parts[] / order[] skeleton, but slot 0 is empty (parts[0] == ""). On its own the base decodes to only ANS-7E37D13 (7 hex digits), which fails the ANS-<16 hex> format.
  • The feature split carries the missing piece as a lightweight config fragment: {"part": "4754DEA01", "part_index": 0} - not itself a full parts puzzle.
  • Reassembly = fold each fragment's part into the base parts[] at its declared part_index, then apply the split codec's ordering.

The split ordering rule (solver _split): join the parts in the index order that sorts by order[i]:

"".join(parts[i] for i in sorted(range(len(parts)), key=lambda i: order[i]))

Exact reconstruction + decode steps

  1. Base64-decode the GM artifact (split_decision_time_trial.apks) -> outer ZIP.
  2. Open the outer ZIP; read members base.apk (challenge artifact, not published) and feature.apk (challenge artifact, not published) (both inner ZIPs).
  3. From base.apk (challenge artifact, not published) read assets/huntress_puzzle.json -> parts = ["", "ANS-7", "E37D13"], order = [2, 0, 1].
  4. From feature.apk (challenge artifact, not published) read assets/huntress_feature.json -> fragment part = "4754DEA01", part_index = 0.
  5. Merge: parts[0] = "4754DEA01" -> parts = ["4754DEA01", "ANS-7", "E37D13"].
  6. Apply the split order. With order = [2, 0, 1], sorting indices by order[i] gives the sequence i=1 (order 0), i=2 (order 1), i=0 (order 2):
    • parts[1] = ANS-7
    • parts[2] = E37D13
    • parts[0] = 4754DEA01
  7. Concatenate -> ANS-7 + E37D13 + 4754DEA01 = AnswerANS-7E37D134754DEA01.
  8. Verify against the answer format ^ANS-[0-9A-F]{16}$ -> PASS (16 hex digits).

Final answer

  • answer AnswerANS-7E37D134754DEA01

Independently reconstructed from the raw artifact bytes (not the solver's output) and confirmed equal to the value the repaired autosolve_mobile.py produced. The Single Solve was accepted CORRECT live by the GM (completion token above).

Notes for Time Trial / Mastery

Time Trial and Mastery artifacts are mutated per attempt (fresh bytes each start), so the exact fragments and order differ per attempt, but the structure is identical: reassemble base + feature split fragments and apply the declared codec. One live ranked Time Trial attempt was observed to deliver a different puzzle with codec: "analysis" (answer computed statically from the DEX) rather than split; that path is handled by a separate decoder (_analysis) and was failing at that moment - tracked outside this writeup. Always derive from the attempt's own downloaded bytes; never reuse this Single Solve value for a timed attempt.