Day 26 - Crash Course (Binary / Reverse Engineering)
GM cid: binary-reverse-engineering-day-26-crash-triage Lane: binary-reverse-engineering (agent-2, WORKSTATION) Modes: Single Solve / Time Trial / Mastery (cumulative d01..d26 config-extraction family)
Challenge nature
"Crash Course" is the Day 26 instalment of the recurring cumulative binary-config extraction mastery. One encrypted evidence.zip (challenge artifact, not published) (AES-256, password infected) carries one deliverable per day (dNN--...). Each answer id is dNN_<suffix> and is derived purely from the real artifact bytes of that day's member, in ZIP central-directory order.
Day 26's own member is a Groovy-compiled Java JAR. On top of the standard HCFG config block that every day in this family embeds, Day 26 adds a crash-triage twist: a crash/trace.json stack-trace file bundled inside the JAR, plus a predicate that ties the trace's frame names back to the JAR's primary classfile method table.
Artifact identification
- Outer container:
evidence.zip(challenge artifact, not published) - AES-256 WinZip (pyzipper, method 99), passwordinfected. - Day 26 member (central-directory order, 1-based):
d26--sample.jar(challenge artifact, not published)- size 4508 bytes, sha256
cb614301daacaf60485acad7abdd00887450366f4a131b4b554fe7c5b7f42d05 - this is
d26_artifact_sha256_1andd26_analysis_format = jar.
- size 4508 bytes, sha256
- JAR contents:
META-INF/MANIFEST.MF->Main-Class: Day26Variant000,Created-By: Huntress deterministic Groovy factoryDay26Variant000.class(challenge artifact, not published) (primary application classfile, 5110 bytes)Day26Variant000$_main_closure1.class(Groovy closure, 2018 bytes)crash/trace.json(118 bytes) - the new crash-triage input
The primary classfile is the Main-Class named by the manifest: Day26Variant000.class (challenge artifact, not published).
Deriving each NEW Day-26 field
d26_analysis_crash_fault_method (exact_text)
Open d26--sample.jar (challenge artifact, not published) as a ZIP, read member crash/trace.json, JSON-parse it, and take the FIRST string of its frames array (the innermost / faulting frame).
frames = ["stageThree", "stageTwo", "stageOne"]- Answer:
stageThree
d26_analysis_crash_frames_match_methods (enum true/false)
Parse the primary classfile (Day26Variant000.class (challenge artifact, not published)) method table (full table incl. <init> and synthetic methods). The predicate is true iff EVERY string in the trace's frames array is a member of that method-name set.
- method-name set (10 entries):
<init>,stageThree,stageTwo,stageOne,main,$getStaticMetaClass,getMetaClass,setMetaClass,$getLookup,getEncodedConfig stageThree,stageTwo,stageOneare all present -> Answer:true
d26_analysis_method_count (integer)
Count of the primary classfile's method table (the classfile methods_count field, parsed via the constant pool). Day26Variant000.class (challenge artifact, not published) declares 10 methods.
- Answer:
10 - (This field was NOT part of the HELD residue - the pre-existing Day-7
analysis_method_counthandler already resolved it; see the root-cause note.)
Standard d26 HCFG config fields
Parse the primary classfile constant pool; for every UTF-8 constant that is Base64-alphabet and at least 80 chars, Base64-decode and accept the first CRC32-valid HCFG record. Record layout: bytes 0..3 ASCII HCFG, byte4 version, byte5 one-byte XOR key, bytes6..7 LE payload length, bytes8..11 LE CRC32 of the decoded payload, payload from byte12. XOR payload with the key, verify CRC32, then parse the decoded UTF-8 JSON.
d26_analysis_config_campaign=BR26-000d26_analysis_config_domain=node-000.day26.example.invalidd26_analysis_config_mutex=Global\HuntressBR26_000d26_analysis_config_url=https://node-000.day26.example.invalid/api/BR26-000d26_analysis_config_crc32_hex=0xfd5b48eb(LE uint32 at HCFG bytes 8..11)d26_analysis_hcfg_version=1(HCFG byte 4)d26_analysis_xor_key_hex=0xb1(HCFG byte 5)
(Full decoded JSON also carries ipv4 198.51.100.10, windows_path, linux_path, service, host_model - not asked by Day 26.)
Final answers per mode
Single Solve (static variant 000) full d26 answer set:
| answer_id | value |
|---|---|
| d26_artifact_sha256_1 | cb614301daacaf60485acad7abdd00887450366f4a131b4b554fe7c5b7f42d05 |
| d26_analysis_format | jar |
| d26_analysis_config_campaign | BR26-000 |
| d26_analysis_config_domain | node-000.day26.example.invalid |
| d26_analysis_config_mutex | Global\HuntressBR26_000 |
| d26_analysis_config_url | https://node-000.day26.example.invalid/api/BR26-000 |
| d26_analysis_config_crc32_hex | 0xfd5b48eb |
| d26_analysis_hcfg_version | 1 |
| d26_analysis_xor_key_hex | 0xb1 |
| d26_analysis_crash_fault_method | stageThree |
| d26_analysis_crash_frames_match_methods | true |
| d26_analysis_method_count | 10 |
Time Trial / Mastery: the GM mutates the variant per attempt (campaign/domain/url/mutex, XOR key, CRC, and the faulting frame name change with the variant id). All answers are byte-derived by the same algorithm above, so the solver reproduces them from each attempt's own bytes; the values above are specific to the Single Solve variant 000 artifact.
Verification
Independently derived (standalone classfile parser + HCFG decoder, not the production solver) and cross-checked against autosolve_binary.compute(start, [evidence_bytes]): all 12 d26 fields MATCH exactly, and the solver held none of them after the repair.