binary: 31 days of a cumulative bundle
the binary lane shipped one evidence zip a day and asked for fields of every member: each day added a tag with one runtime or one technique, and every earlier tag came back, often under new field names. it moved from orientation (headers, symbols, sections) through a validated configuration blob in a new carrier each day, to unpacking, role pairs and crash dumps, and from day 28 to questions that spell their own rule. the solver became a cumulative dispatcher: a producer per field, a configuration search over every carrier, and a reader for the spelled recipes.
- 31challengesone a day, days 1 to 31
- 93flagssingle, time trial and mastery
- 42 smedian singletime trial 57.6 s, mastery 1:04; release to flag
- 65%flags by autopilot60 of 93
- 279inventory items51 graded, 228 not yet graded
- 13 of 27covered at releasedays 5 to 31; 10 partial, 2 cold start, 1 long, 1 unknown
- 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 evidence.zip a day, cumulative: each day adds a dNN- tag (one runtime or one technique) with ids dNN_analysis_<field> and dNN_artifact_sha256_K, and every older tag comes back, sometimes under new field names.
the single's answer ids, from the day's test fixture. hover a bar for the tag count and the mastery size.
days 1 and 2, orientation. a c elf's headers, symbols, sections and a return constant (elf aware), then c++ symbols and an xor configuration blob across an elf and a pe (mangled).
days 3 to 7, the tagged bundle. from day 3 every member family carried a dNN- tag and eight fields: .net metadata and native configs (table manners), go (go fish), rust (rust belt), a jar with its config in the constant pool (pool party) and kotlin (routine check).
days 8 to 16, ten fields a tag. swift, with a base64 config literal and answers that changed kind (swift justice); nim (nimble); one zig program as an elf and a pe (zig zag); d (d-day); free pascal (pascal's wager); crystal (crystal clear); objective-c on linux (selective memory); one program built twice with a role in the field name (stripped); webassembly compiled twice (wasm up).
day 17, the long day. twelve fields a tag, and the old tags came back under new names: where the configuration is stored, runtime markers, a class's access word (decoder ring). the single took 1h41m, the longest of any lane outside day 1's late start.
days 18 to 27, techniques. control flow in a fortran tag (flow state), a hashed packed overlay (jack in the box), a resource overlay with scratch after it (resourceful), an ocaml loader and its plugin (shared custody), a managed module at the p/invoke crossing (bridge troll), anti-analysis predicates (trust issues), two scala builds (spot the difference), two clojure builds (out of bounds), a groovy jar with its own crash dump (crash course) and the compiler as a role word (compiler says what).
day 28, questions as recipes. fourteen fields a tag: 32 new names on old tags at once, most spelling their own rule (true when the final bytes contain a literal, count the symbol names a regex matches, join and hash). the single took 13:37, and the lane gained a reader for the question's own recipe (family resemblance).
days 29 to 31, configs under new magics. one program built twice (fraternal twins); a config record under a new magic at the end of three neko modules (campaign trail); one more magic, nested one level deeper (final boss).
the bundle by day, from the test fixtures (the challenge column is the organizer's name for the day):
| day | the day's challenge | fields a tag | single fields | mastery | post |
|---|---|---|---|---|---|
| 1 | c elf orientation | - | 9 | - | elf aware |
| 2 | cpp and pe orientation | - | 17 | 2 sets, 34 fields | mangled |
| 3 | managed configuration | 8 | 24 | 2 sets, 48 fields | table manners |
| 4 | go runtime fingerprints | 8 | 32 | 2 sets, 64 fields | go fish |
| 5 | rust runtime shapes | 8 | 40 | 2 sets, 80 fields | rust belt |
| 6 | java bytecode loader | 8 | 48 | 2 sets, 96 fields | pool party |
| 7 | kotlin staging logic | 8 | 56 | 2 sets, 112 fields | routine check |
| 8 | swift network configuration | 10 | 80 | 5 sets, 400 fields | swift justice |
| 9 | nim generated runtime | 10 | 90 | 5 sets, 450 fields | nimble |
| 10 | zig cross platform services | 10 | 100 | 3 sets, 300 fields | zig zag |
| 11 | d collection planner | 10 | 110 | 3 sets, 330 fields | d-day |
| 12 | pascal archive stager | 10 | 120 | 3 sets, 360 fields | pascal's wager |
| 13 | crystal dns configuration | 10 | 130 | 3 sets, 390 fields | crystal clear |
| 14 | objective c persistence descriptor | 10 | 140 | 3 sets, 420 fields | selective memory |
| 15 | assembly and symbol loss | 10 | 150 | 5 sets, 750 fields | stripped |
| 16 | webassembly optimization equivalence | 10 | 160 | 5 sets, 800 fields | wasm up |
| 17 | encoded configuration recovery | 12 | 204 | 5 sets, 1020 fields | decoder ring |
| 18 | control flow reconstruction | 12 | 216 | 4 sets, 864 fields | flow state |
| 19 | static unpacking | 12 | 228 | 5 sets, 1140 fields | jack in the box |
| 20 | resources and overlays | 12 | 240 | 5 sets, 1200 fields | resourceful |
| 21 | shared library boundaries | 12 | 252 | 5 sets, 1260 fields | shared custody |
| 22 | managed native bridge | 12 | 264 | 6 sets, 1584 fields | bridge troll |
| 23 | anti analysis recognition | 12 | 276 | 7 sets, 1932 fields | trust issues |
| 24 | patch diffing | 12 | 288 | 8 sets, 2304 fields | spot the difference |
| 25 | synthetic vulnerability root cause | 12 | 300 | 9 sets, 2700 fields | out of bounds |
| 26 | crash triage | 12 | 312 | 10 sets, 3120 fields | crash course |
| 27 | compiler attribution | 12 | 324 | 11 sets, 3564 fields | compiler says what |
| 28 | family clustering | 14 | 392 | 12 sets, 4704 fields | family resemblance |
| 29 | variant diffing | 14 | 406 | 13 sets, 5278 fields | fraternal twins |
| 30 | multi binary campaign | 14 | 420 | 14 sets, 5880 fields | campaign trail |
| 31 | reversing gauntlet | 14 | 434 | 15 sets, 6510 fields | final boss |
coverage
this lane's row of the coverage grid. autopilot answered 13 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 | unknown | no gaps row: autopilot's pass on it failed before its dry run (ModuleNotFoundError: No module named 'pefile') | 0:28, helper |
| 6 | partial | 8 fields (d06-analysis, d06-artifact): a KeyError on 06 |
1:39, helper |
| 8 | partial | 11 fields in 4 families (d02, d06, d07, d08): no producer for compression_methods, has_cpp_typeinfo, has_cpp_vtable |
1:47, helper |
| 9 | partial | 1 field (d09-analysis): no producer for hcfg_offset |
0:56, helper |
| 10 | partial | 1 field (d10-analysis): no producer for has_hcfg_section |
0:56, helper |
| 15 | partial | 8 fields (d15-analysis): no producer for stripped_architecture, stripped_config_campaign, stripped_config_domain |
0:57, lane fixer |
| 17 | long | 12 fields in 11 families (d02, d04, d05, d06, d07, d08, …): no producer for access_flags, has_coroutine_runtime, has_go_runtime |
1h41m, helper |
| 19 | partial | 8 fields (d19-analysis): no producer for overlay_offset, overlay_size; no valid hcfg blob in any member |
0:49, autopilot |
| 20 | partial | 1 field (d20-analysis): no producer for hcfg_resource_size |
0:39, autopilot |
| 21 | partial | 6 fields (d21-analysis): no producer for loader_machine, plugin_config_campaign, plugin_config_domain |
0:17, autopilot |
| 26 | partial | 2 fields (d26-analysis): no producer for crash_fault_method, crash_frames_match_methods |
0:54, autopilot |
| 28 | cold start | 32 fields in 16 families (d01, d03, d05, d06, d09, d10, …): no producer for class_name, cli_runtime, conditional_branch_opcode_count |
13:28, parent |
| 30 | cold start | 8 fields (d30-analysis): no valid hcfg blob in any member; an ungraded binary format, neko_bytecode |
3:47, autopilot |
| 31 | partial | 10 fields (d31-analysis): no producer for config_campaign, config_domain, config_mutex |
1:01, lane fixer |
the tooling that grew for it
the lane's tool page, elf, c++, hcfg, pe/cli, and cumulative binary dispatch, opens with what the solver did by day 3 and adds a section for every day its code changed:
- day 4: field producers instead of day analyzers, build facts
- day 5: day 5 additions
- day 6: day 6 additions
- day 7: naming the format from the bytes, dex constants, mach-o, webassembly, failures are errors
- day 8: hcfg in a base64 literal, answers by kind, fields for old tags, faster on large members
- day 9: one carrier search, the offset, old tags answer from their format or fail, faster across sets, stripped nim builds
- day 10: section-table questions, runtime markers that survive strip, jvm, kotlin and swift structure, the dynamic trace
- day 11: where an offset sits, fewer external tool runs
- day 12: fields from the other lanes, .net columns by name
- day 15: day 15 additions
- day 16: day 16 additions
- day 17: the next keys of each record, the storage form of the configuration blob, c++ names on a pe build, runtime markers and a class's access word
- day 19: finding the container boundary, proving the unpacking step, feeding the existing record parser
- day 20: a header with scratch after the data, the question's words for the layout
- day 21: role pairs across extensions
- day 26: a jar's crash dump
- day 28: questions read as recipes, readers that dispatch on the member's format, the family and its false friend
- day 30: a configuration record under a renamed magic, every carrier stage without a magic, producers for techniques never asked by name, the call graph inside a timed set
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 | elf aware | 2h43m | 3h03m | 3h04m |
| 2 | mangled | 7:10 | 10:22 | 18:47 |
| 3 | table manners | 9:37 | 10:59 | 11:01 |
| 4 | go fish | 2:31 | 3:08 | 4:17 |
| 5 | rust belt | 0:28 | 0:30 | 0:32 |
| 6 | pool party | 1:40 | 1:43 | 1:45 |
| 7 | routine check | 0:05 | 0:09 | 0:12 |
| 8 | swift justice | 1:54 | 2:33 | 5:40 |
| 9 | nimble | 1:03 | 1:34 | 1:41 |
| 10 | zig zag | 1:02 | 1:06 | 1:10 |
| 11 | d-day | 0:02 | 0:06 | 0:10 |
| 12 | pascal's wager | 0:06 | 0:10 | 0:14 |
| 13 | crystal clear | 0:05 | 0:10 | 0:14 |
| 14 | selective memory | 0:05 | 0:09 | 0:13 |
| 15 | stripped | 1:02 | 2:24 | 2:31 |
| 16 | wasm up | 0:04 | 0:10 | 0:16 |
| 17 | decoder ring | 1h41m | 1h42m | 1h45m |
| 18 | flow state | 0:03 | 0:07 | 0:13 |
| 19 | jack in the box | 0:54 | 0:58 | 1:04 |
| 20 | resourceful | 0:42 | 0:46 | 0:51 |
| 21 | shared custody | 0:22 | 0:24 | 0:29 |
| 22 | bridge troll | 0:08 | 0:15 | 0:24 |
| 23 | trust issues | 0:04 | 1:18 | 1:25 |
| 24 | spot the difference | 0:07 | 0:12 | 0:19 |
| 25 | out of bounds | 0:06 | 0:12 | 0:21 |
| 26 | crash course | 1:02 | 1:06 | 1:17 |
| 27 | compiler says what | 0:09 | 0:17 | 0:31 |
| 28 | family resemblance | 13:37 | 26:04 | 31:20 |
| 29 | fraternal twins | 0:07 | 0:11 | 0:24 |
| 30 | campaign trail | 3:58 | 4:01 | 4:10 |
| 31 | final boss | 1:08 | 1:47 | 1:55 |
{generated by a clanker}