JNI Boundary (mobile-android-day-16-jni-boundary)
Lane: mobile-android. Case MOB-16-6B50835383, package com.huntress.mobile.d16.v6b5083538392.
Prompt
Identify a Java-to-native type or length assumption that changes backend authorization. Submit only the exact backend answer code (ANS- plus 16 uppercase hex).
Solve
- artifact_0.bin is an APK (7 members: manifest, classes.dex, lib/x86_64/libarena.so, assets/huntress_puzzle.json, META-INF signing files).
- assets/huntress_puzzle.json = {"schema":"huntress.mobile.puzzle.v1","day":16,"codec":"native","data":"AnswerANS-901682D7DCA93404"}.
- Codec "native" is a pass-through (the data field is already the answer); the native library libarena.so is the flavour layer (Java int/length assumption crossing the JNI boundary).
- autosolve_mobile.py handled it with no extension (same spine as earlier days).
Result
- Single Solve: CORRECT - AnswerANS-901682D7DCA93404
- Time Trial: CORRECT (autosolve, derived from that attempt's own bytes)
- Mastery: CORRECT (autosolve, derived from that attempt's own bytes)
Notes
The Android topic is cosmetic; the real layer is the puzzle codec in assets/huntress_puzzle.json. A new codec name ("native") resolved as plain/pass-through.