Tactical LogHuntress CTF 2026 // team archive

Days / Day 09 / Mobile Android / Trust Everyone

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

Trust Everyone

Mobile Android SSTTMM Modes reported CORRECT in this write-up

Challenge

  • Category: Mobile / Android (Day 09). Game Master ID mobile-android-day-09-trust-everyone.
  • Prompt: "Exploit a challenge CA accepted by a permissive trust implementation."
  • Modes: Single Solve, Time Trial, Mastery - all CORRECT (3/3).
  • Answer form: one field, answer, derived from the assigned APK's own bytes.

Artifacts

  • The assigned APK for this attempt (dynamic per attempt; analysed from its own bytes, not reused across attempts).

Triage

Android-puzzle family: the APK ships a permissive certificate-trust implementation (a custom TrustManager/network-security-config that accepts a challenge-planted CA). The answer is recovered from the APK's bundled trust material / puzzle asset, not by running the app.

Investigation

Solved by the generic adapter challenges/_lib/autosolve_mobile.py at claim: it unpacks the APK, reads the embedded puzzle/trust asset, and applies the family's codecs (the same caesar/xor/split decoders that have resolved the mobile lane D01-D08) to produce the single answer value. No device or dynamic execution.

Flags (GM completion tokens, per mode)

  • single_solve Tokene2fe688d34d9994b4292135c614de8a8
  • time_trial Token1dd172fdb7ad5e948660fb089c8a5b6c
  • mastery Token672cf9006189c5a1bd0d85dd7ff5708d

Minimal Reproduction

wsl python3 challenges/_lib/autosolve.py 9 mobile-android-day-09-trust-everyone mobile-android - start, download the APK, decode the embedded trust/puzzle asset, submit answer.

Lessons Learned

  • The "permissive trust" theme is framing; the solve is static recovery from the APK's own bytes. The mobile adapter handled all three modes directly, consistent with its D01-D08 track record.