Tactical LogHuntress CTF 2026 // team archive

Days / Day 15 / Mobile Android / Native Library Secrets

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

Native Library Secrets

Mobile Android SSTTMM Modes reported CORRECT in this write-up

Native Library Secrets (Day 15, mobile-android)

GM id: mobile-android-day-15-native-library-secrets Case: MOB-15-FB8CA304AC, package com.huntress.mobile.d15.vfb8ca304ac31

Result

Single Solve, Time Trial and Mastery all CORRECT via autosolve_mobile.py (2.4s / 2.4s / 3.2s). No extension needed.

Accepted answer (Single attempt): AnswerANS-E28C9614AEF73B8F

Analysis

  • APK has 7 entries: AndroidManifest.xml, classes.dex, assets/huntress_puzzle.json, lib/x86_64/libarena.so, META-INF signature files.
  • assets/huntress_puzzle.json = {"schema":"huntress.mobile.puzzle.v1","day":15,"codec":"native","data":"AnswerANS-E28C9614AEF73B8F"}. The codec name "native" means the answer code lives in the challenge-owned JNI library; the asset data matches it.
  • libarena.so (rodata) contains the string AnswerANS-E28C9614AEF73B8F, with exported symbols huntress_arena_secret / huntress_arena_day and arena_value.
  • classes.dex holds the other half of the split configuration: the client_secret/proof URL fragment and the label "Day-15:jni_secret:challenge-owned JNI shared library", plus NativeLibrarySecrets class (JNI boundary).
  • Takeaway: the "native" codec is a repeat of the plain pattern (data IS the answer, cross-checked against the .so).

Method

Derive from each attempt's own APK bytes (puzzle is per-attempt, never hard-coded); one extractor serves all three modes.