Day 21 - Package Deal (metadata-forensics)
Challenge id: metadata-forensics-day-21-package-deal Question: Determine apk.package_name for mobile-001.apk (artifact: metadata-day-21-evidence.zip -> mobile-001.apk).
Result
- Single Solve: CORRECT
- Time Trial: CORRECT (ranked)
- Mastery: CORRECT (ranked)
Method (static analysis only, nothing executed)
- The artifact is a zip holding one member, mobile-001.apk (8535 bytes).
- The apk is itself a zip: AndroidManifest.xml, classes.dex, META-INF/FIXTURE-.SF/.RSA/MANIFEST.MF.
- AndroidManifest.xml is binary XML (AXML). Parsed the string pool and the start-element attributes. The root
manifestelement carriespackage. - Single answer (exact_text, trim): com.huntress.arena.p08281778 (application label in the same manifest: "Huntress Evidence 08281778"; versionName 1.0, versionCode 1, minSdk/targetSdk 23).
The answer comes from the manifest bytes, not from the friendly filename.
Tooling added
- challenges/_lib/apk_meta.py: minimal AXML reader; registers apk.package_name (+ aliases package, version_name, version_code, min_sdk_version, target_sdk_version, application_label, app_label). Accepts a bare apk or a zip that wraps an .apk.
- challenges/_lib/autosolve_metadata.py: registers apk_meta after the other optional modules (never overrides an existing field).
- Time Trial and Mastery use the same shape on fresh bytes, so the same extractor solved both.
Notes for later days
- Likely follow-ups on this format: other manifest fields, rebuild-vs-clone comparisons (same package, different signing cert / dex), "borrowed product name" = application label. Signing data lives in META-INF/*.RSA (PKCS#7) if a certificate field is asked.