Tactical LogHuntress CTF 2026 // team archive

Days / Day 13 / Mobile Android / Keystore Misuse

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

Keystore Misuse

Mobile Android SSTTMM Modes reported CORRECT in this write-up

Keystore Misuse (mobile-android, Day 13)

GM id: mobile-android-day-13-keystore-misuse Case: MOB-13-BECFE8C675, package com.huntress.mobile.d13.vbecfe8c67588

Prompt

Recover data protected by an app-controlled wrapping key despite nominal Keystore use. Submit only the exact backend answer code (ANS- plus 16 uppercase hex).

Method

  1. The artifact is an APK (6 entries: manifest, classes.dex, a DER certificate, text files, assets/huntress_puzzle.json).
  2. assets/huntress_puzzle.json = {"schema":"huntress.mobile.puzzle.v1","day":13,"codec":"base64","data":"QU5TLTc3Mzc2MkU4NTc5NzA2NEM="}.
  3. Applying the declared codec (base64) to data yields the answer code.
  4. Theme (flavour): the wrapping key is app-controlled, so Keystore use is nominal only; the puzzle mechanism is the codec, not the Android theme.

Result

Single Solve: CORRECT (autosolve_mobile, 2.0 s) Time Trial: CORRECT (autosolve_mobile, 2.1 s) Mastery: CORRECT (autosolve_mobile, 4.4 s)

Single-attempt answer (per-attempt puzzle, timed variants differ): AnswerANS-773762E85797064C

Notes

  • Codec was base64, a repeat of Day 9. The prepared autosolve_mobile adapter covered it with no extension.
  • Lesson: none new.