Tactical LogHuntress CTF 2026 // team archive

Days / Day 12 / Mobile Android / SQLite Assumptions

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

SQLite Assumptions

Mobile Android SSTTMM Modes reported CORRECT in this write-up

SQLite Assumptions - Day 12 (mobile-android)

GM id: mobile-android-day-12-sqlite-assumptions Case: MOB-12-4B4FA1A323, package com.huntress.mobile.d12.v4b4fa1a3235d

Result

  • single_solve: CORRECT (AUTOSOLVE, 1.5 s)
  • time_trial: CORRECT (AUTOSOLVE, 2.3 s, derived from that attempt's own APK bytes)
  • mastery: CORRECT (AUTOSOLVE, 2.4 s)

Method

  1. Unzipped the APK (artifact_0.bin): AndroidManifest.xml, classes.dex, META-INF signing files, assets/huntress_puzzle.json.
  2. assets/huntress_puzzle.json = {"schema":"huntress.mobile.puzzle.v1","day":12,"codec":"hex","data":"414e532d30333946304439303731313131303530"}.
  3. Codec "hex" (a codec already covered by autosolve_mobile.py): hex-decode data -> ASCII.
  4. Decoded Single Solve answer: AnswerANS-039F0D9071111050 (the GM accepted it as CORRECT via AUTOSOLVE).

The SQLite / authorization theme is flavour; the puzzle codec is the answer. The puzzle is per attempt, so timed attempts were derived by the autosolver from each attempt's own APK rather than reusing this value.

Notes

  • No extension of autosolve_mobile.py was needed: the existing hex codec handled today's variant.
  • A board.py todo check hit GM HTTP 429 rate_limited; not retried in a loop (rate-limit rule).