Challenge
- Category: Mobile Android (Day 05), GM id
mobile-android-day-05-backup-spill - Prompt: "Extract synthetic application state admitted by a flawed backup boundary."
- Question shape:
For case MOB-05-<id> in package com.huntress.mobile.d05.v<id> ... Submit only the exact backend answer code returned for this case. - Flag format:
ANS-followed by exactly 16 uppercase hex characters (answer code, notflag{}) - Same recurring family as Day 04's "Pending Intent Relay": a small synthetic fixture APK whose real answer is bundled in a JSON puzzle asset, not derived by exploiting the themed Android mechanic (a "flawed backup boundary" here, a "mutable PendingIntent relay" on Day 04) at runtime.
Artifacts
backup_spill.apk(challenge artifact, not published) -AndroidManifest.xml,classes.dex(challenge artifact, not published),assets/huntress_puzzle.json, fixture-signedMETA-INF.
Triage
Per the established pattern for these fixture APKs: check assets/*.json first before any decompilation - the dex is small and decorative, the real answer lives in the bundled puzzle asset.
Investigation
- Unzip the APK; read
assets/huntress_puzzle.json:{"schema": "huntress.mobile.puzzle.v1", "day": 5, "codec": "split", "data": "", "parts": ["0A353BE7B", "ANS-5", "709E18"], "order": [2, 0, 1]} codec = "split": the real string ispartsreassembled in the order given byorder-order[i]is the position ofparts[i]in the final string, so sort indices by theirordervalue and concatenate:parts, order = p["parts"], p["order"] "".join(parts[i] for i in sorted(range(len(parts)), key=lambda i: order[i]))- This reassembles
orderpositions 0,1,2 ->parts[1]="ANS-5",parts[2]="709E18",parts[0]="0A353BE7B"-> AnswerANS-5709E180A353BE7B.
Flag Recovery
Reassembling the split-codec puzzle parts by their declared order yields AnswerANS-5709E180A353BE7B (16 uppercase hex characters after the ANS- prefix, matching the required answer format exactly) - derived directly from the bundled asset, independently reproduced.
Flag
<REDACTED_TOKEN>
(Single Solve, Time Trial, and Mastery were all confirmed CORRECT by the Game Master on 2026-10-05 - done.json lists all three modes solved. The raw completion tokens were not preserved locally at solve time, hence the redacted placeholder; the decode above is independently re-verified against the actual staged artifact bytes.)
Minimal Reproduction
import zipfile, json
z = zipfile.ZipFile('backup_spill.apk')
p = json.loads(z.read('assets/huntress_puzzle.json'))
parts, order = p['parts'], p['order']
print(''.join(parts[i] for i in sorted(range(len(parts)), key=lambda i: order[i])))
General solver (handles split/reverse/plain/base64 codec variants and nested-APK artifacts): scripts/solve_backup_spill.py in this folder.
Lessons Learned
- This "mobile fixture puzzle asset" family (Day 04 Pending Intent Relay, Day 05 Backup Spill) is now recurring with a growing codec set (
xor,split,reverse,plain,base64seen so far) - always checkassets/*.jsonfor aschema: huntress.mobile.puzzle.*document before any dex/manifest reversing; the themed Android mechanic in the prompt is flavor, not the actual exploitation path. splitcodec:order[i]gives the position ofparts[i], not the reverse - sort indices byordervalue, don't naively zippartswithorderas (value, index) pairs.