mobile: 31 days of a puzzle inside an app
the mobile lane asked one thing all month: an ANS- code decoded from the puzzle json an apk carries in its assets. the manifest, deep links, intents and each day's story were flavor; the codec named in the puzzle was the challenge. it cycled through seven names for two weeks, picked up names outside the cycle from day 15, moved the timed tiers to a code the app's own dex computes from day 23, and ended on framed, keyed and layered codecs. the solver became a codec registry with keys fitted from the ANS- prefix, a bounded layer peel and a dalvik interpreter that runs the app's code.
- 31challengesone a day, days 1 to 31
- 93flagssingle, time trial and mastery
- 2.6 smedian singletime trial 5.1 s, mastery 8.5 s; release to flag
- 77%flags by autopilot72 of 93
- 227inventory items46 graded, 181 not yet graded
- 21 of 27covered at releasedays 5 to 31; 5 partial, 1 cold start
- autopilot
- lane fixer
- helper
- parent
- other
the scale stops at ten minutes; a dashed bar is a day beyond it (hover for the time). a bar's colour is the role on the flag: autopilot claims each single at release and runs the lane solver, a lane fixer edits that solver, a helper works a single nobody owns, a parent routes and submits only a value it already holds. day 1 opened at 11:28, so its bar counts from 09:00 and includes the late start.
how the family evolved
one answer id, answer: ANS- and 16 uppercase hex digits, decoded from assets/huntress_puzzle.json ({schema, codec, data[, key]}). the question never changed shape.
days 1 to 7, the cycle. plain (exported trust), reverse (deep link drift), base64 (intent injection), a keyed xor (pending intent relay), split parts put back by an order list (backup spill), hex (provider paths) and a caesar shift on the answer text (webview bridge).
days 8 to 14, the cycle again, out of order. reverse, base64, split, xor, hex, base64 and caesar under stories of cleartext traffic, trust managers, network config, local stores, sqlite, a keystore and crypto (cleartext session, trust everyone, network config split, local secrets, sqlite assumptions, keystore misuse, predictable crypto). every story was only a story; autopilot took all seven singles at release.
days 15 to 22, names outside the cycle. native twice (native library secrets, jni boundary), indexed, one character per index (name collapse), a keyed xor again (encrypted strings), reflection, a name read by its answer's shape (reflection maze), dynamic, the code in a second dex (loaded later), then reverse (debug me if you can) and base64 (root of trust). from day 15 mastery mixed older codecs into its sets.
days 23 to 26, a computed code. the timed tiers moved to a second puzzle schema with no data: the app's dex computes the code, so a dalvik interpreter went in on day 23 (hook line and signal). the single kept a first-schema codec on those days, and day 26 shipped the app as a base apk and a feature split (split decision).
days 27 to 31, frames, tables and layers. base64 on the single with an eleven-set mastery of older codecs (dependency surface); a framed packet with a checksum trailer, 14:12 to the single (protocol reconstruction); a byte table keyed by its index (white box key recovery); reversed bytes under a walking xor key and base64 (layered protections); on day 31 the computed code reached the single too (mobile arena gauntlet).
the codec in each tier's puzzle json, read from the saved apks (a mastery cell counts its sets and their distinct codecs):
| day | the single's codec | the time trial's | mastery | post |
|---|---|---|---|---|
| 1 | plain |
plain |
3 sets, all plain |
exported trust |
| 2 | reverse |
reverse |
3 sets, all reverse |
deep link drift |
| 3 | base64 |
base64 |
3 sets, all base64 |
intent injection |
| 4 | xor |
xor |
3 sets, all xor |
pending intent relay |
| 5 | split |
split |
3 sets, all split |
backup spill |
| 6 | hex |
hex |
3 sets, all hex |
provider paths |
| 7 | caesar |
caesar |
3 sets, all caesar |
webview bridge |
| 8 | reverse |
reverse |
5 sets, all reverse |
cleartext session |
| 9 | base64 |
base64 |
5 sets, all base64 |
trust everyone |
| 10 | split |
split |
3 sets, all split |
network config split |
| 11 | xor |
xor |
3 sets, all xor |
local secrets |
| 12 | hex |
hex |
3 sets, all hex |
sqlite assumptions |
| 13 | base64 |
base64 |
3 sets, all base64 |
keystore misuse |
| 14 | caesar |
caesar |
3 sets, all caesar |
predictable crypto |
| 15 | native |
native |
5 sets, 3 codecs | native library secrets |
| 16 | native |
native |
5 sets, 5 codecs | jni boundary |
| 17 | indexed |
indexed |
5 sets, 5 codecs | name collapse |
| 18 | xor |
xor |
5 sets, 5 codecs | encrypted strings |
| 19 | reflection |
reflection |
5 sets, 5 codecs | reflection maze |
| 20 | dynamic |
dynamic |
5 sets, 5 codecs | loaded later |
| 21 | reverse |
reverse |
5 sets, 4 codecs | debug me if you can |
| 22 | base64 |
base64 |
6 sets, 4 codecs | root of trust |
| 23 | xor |
analysis |
7 sets, all analysis |
hook line and signal |
| 24 | split |
analysis |
8 sets, all analysis |
emulator alibi |
| 25 | hex |
analysis |
9 sets, all analysis |
integrity signals |
| 26 | split |
analysis |
10 sets, all analysis |
split decision |
| 27 | base64 |
base64 |
11 sets, 8 codecs | dependency surface |
| 28 | packet |
analysis |
12 sets, all analysis |
protocol reconstruction |
| 29 | table |
analysis |
13 sets, all analysis |
white box key recovery |
| 30 | layered |
analysis |
14 sets, all analysis |
layered protections |
| 31 | analysis |
analysis |
15 sets, all analysis |
mobile arena gauntlet |
coverage
this lane's row of the coverage grid. autopilot answered 21 of the 27 singles from day 5 on with no gaps row; the table lists the rest. closed in runs from autopilot's gaps row to the single's flag.
- covered at release
- partial, under 3 min
- cold start, 3 to 15 min
- long, over 15 min
- no release pass or unknown
hover a cell for the time, the role on the flag and what was missing. grey on days 1 to 4: the release pass started on day 5.
| day | at release | what was missing | closed in |
|---|---|---|---|
| 5 | partial | 1 field (answer): no decoding path found |
1:15, helper |
| 17 | partial | 1 field (answer): no decoding path found |
0:16, lane fixer |
| 20 | partial | 1 field (answer): no decoding path found |
0:00, autopilot |
| 26 | partial | 1 field (answer): the split parts did not join |
0:26, parent |
| 28 | cold start | 1 field (answer): no decoding path found |
14:09, parent |
| 29 | partial | 1 field (answer): no decoding path found |
0:14, lane fixer |
the tooling that grew for it
the lane's tool page, android apk puzzle extraction, opens with what the solver did by day 3 and adds a section for every day its code changed:
- day 4: keyed codecs, rc4, vigenere and compressed payloads
- day 5: day 5 additions
- day 7: keyed steps on raw text, codec names from other lanes
- day 8: more codec names, list data
- day 9: any registry transform is a codec name, every reading of the data and the key, keys from the known prefix, tolerant answer extraction, asset and field guards
- day 10: split, again and changed, manifest and network security config
- day 11: url-safe base64 under a keyed step
- day 12: app fields from the other lanes, two more codec names
- day 13: aes codecs
- day 14: transpositions, substitutions and a key the app holds
- day 16: day 16 additions
- day 17: one character per index
- day 18: chacha20, triple des and blowfish beside aes
- day 20: data that names a member, the normal reader first
- day 21: every manifest and signer scalar by name
- day 23: a dalvik interpreter for computed codes, native pieces under an emulator, assets, resources and a loaded dex, the dex view in triage
- day 26: a bundle of split apks is one app, splitSourceDirs and a ZipFile over a split, a split puzzle's missing part, a missing record field names its builder
- day 28: the packet codec: a frame layout chosen by its checksums, an answer-shape scan, a framework layer for the dalvik interpreter
- day 29: the table codec: a byte table keyed by its index
- day 30: the layered codec: reversed bytes under a walking key, a bounded layer peel, two keyed layers and an unnamed block step, an ambiguous stack and the unstripped root
every post, in order
times run from the 09:00 et release to each tier's flag; day 1 opened at 11:28 and counts from 09:00.
| day | post | single | time trial | mastery |
|---|---|---|---|---|
| 1 | exported trust | 2h48m | 2h48m | 2h50m |
| 2 | deep link drift | 9:56 | 10:37 | 10:40 |
| 3 | intent injection | 0:30 | 0:50 | 1:00 |
| 4 | pending intent relay | 0:49 | 1:22 | 1:31 |
| 5 | backup spill | 1:16 | 1:23 | 1:25 |
| 6 | provider paths | 0:02 | 0:04 | 0:06 |
| 7 | webview bridge | 0:04 | 0:08 | 0:11 |
| 8 | cleartext session | 0:04 | 5:22 | 5:23 |
| 9 | trust everyone | 0:04 | 0:06 | 0:08 |
| 10 | network config split | 0:04 | 0:06 | 0:07 |
| 11 | local secrets | 0:01 | 0:03 | 0:05 |
| 12 | sqlite assumptions | 0:02 | 0:03 | 0:05 |
| 13 | keystore misuse | 0:02 | 0:04 | 0:06 |
| 14 | predictable crypto | 0:02 | 0:05 | 0:07 |
| 15 | native library secrets | 0:02 | 0:04 | 0:06 |
| 16 | jni boundary | 0:03 | 0:05 | 0:08 |
| 17 | name collapse | 0:19 | 0:34 | 0:36 |
| 18 | encrypted strings | 0:01 | 0:04 | 0:05 |
| 19 | reflection maze | 0:02 | 0:04 | 0:06 |
| 20 | loaded later | 0:02 | 0:04 | 1:08 |
| 21 | debug me if you can | 0:01 | 0:03 | 0:06 |
| 22 | root of trust | 0:02 | 0:06 | 0:08 |
| 23 | hook line and signal | 0:02 | 5:22 | 5:24 |
| 24 | emulator alibi | 0:02 | 0:04 | 0:07 |
| 25 | integrity signals | 0:02 | 0:05 | 0:07 |
| 26 | split decision | 0:29 | 3:04 | 3:18 |
| 27 | dependency surface | 0:02 | 0:04 | 0:08 |
| 28 | protocol reconstruction | 14:12 | 16:15 | 16:18 |
| 29 | white box key recovery | 0:17 | 1:12 | 1:16 |
| 30 | layered protections | 0:03 | 0:05 | 0:09 |
| 31 | mobile arena gauntlet | 0:03 | 0:05 | 0:09 |
{generated by a clanker}