make it make sense: a makefile as one more carrier

huntress ctf 2026, day 29 · script analysis · all three modes

tools used: script analysis and timed-attempt pipeline.

"unseen makefile variants and their prior-language build chains differ in layered variables and target flow. diff them carefully, and keep only the tradecraft conclusions that hold up across every variant." the day's new specimens were four makefiles, and the questions about them were the family's usual descriptor fields under a new carrier.

the key insight is that none of the story became a field. a makefile is a carrier like the terraform file of day 28 or the dockerfile of day 27: the analysis header sits in it under one of the known encodings, and the same descriptor reader answered every field without being told what make is or how its variables layer.

challenge shape

single         1747 fields   the cumulative families of every earlier
                             day plus the makefile specimens' descriptors
time trial     1833 fields   183 samples renamed <6 hex>.<ext>, layered
                             headers and composite fields as on day 23
mastery       23829 fields   thirteen sets

the makefile fields are eleven descriptor fields (adapter, attack, campaign, a file path or url, host profile, next language, obfuscation, role, stage count, stage profile, steps) for each of four specimens: a benign utility, a downloader, a launcher and a staged chain.

artifact anatomy

the evidence zip's members are aes-encrypted under the lane's standing password (infected, as on every day; 7z x -pinfected), so the first step is the archive reader's, not make's. each .mk file is a few lines that would do nothing if run:

comment line     # HUNTRESS_ANALYSIS_V1:<CODEC>-<payload>
assignment       HUNTRESS_DESCRIPTOR_<hex> := <the same payload>
.PHONY target    analyze-<hex>, whose one recipe line is @:

the four single-mode files used four codecs (B64, HEX, HB64, FRAG); in the time trial every makefile header was day 23's layered LYR-<layers>-<payload>.

the descriptor is the family's pipe-separated key=value record (role, attack, adapter, host and stage profiles, the next language, the stage count, the ordered steps, the campaign, a url or file path). it appears twice, once in the comment and once as the variable's value, and both copies agree. the target exists so the file parses as a makefile; it builds nothing.

extraction method

the script analysis reader treats any carrier the same way: find the header under its codec in a comment or a literal, parse the descriptor, and read every field from it by key; role and attack are used verbatim when the descriptor states them:

from ctfkit.hlib import specimen

found = specimen.find(text)                 # header first, then the slower search
fields = specimen.answers(text, language)   # language from the field id

the header finder looks for the HUNTRESS_ANALYSIS_V1: marker and reads the codec name and payload after it; a makefile's # comment and := assignment are just text around it, so the reader needed no makefile-specific code and received none on day 29.

validation and answer formatting

the label fields are exact text; the reader submits the descriptor's own spelling first and the family's confirmed alternatives after it. counts are base-10 integers, the steps are an ordered list with the question's > separator, urls and paths are submitted as stored. every one of the 1747 fields read on the first run of the single.

failed approaches and pivots

none on day 29.

automation across modes

the solve took 0.59 seconds on the single, 0.21 seconds on the time trial and 1.57 seconds for the mastery's thirteen sets; no field came back rejected.

lessons

solve times

public scoreboard · day 29 finish: below top 10

  • 0:05.1single#2 of 141 solvers
  • 0:08.7time trial#2 of 139 solvers
  • 0:15.9mastery#2 of 135 solvers
  • #61team day finishof 116 teams that cleared it, in 34:38.6
  • #3single orderof the day's 7, by our flag time

from the public scoreboard: 09:00 et release to our flag; the table below counts from our attempt's start.

from when we started working on the mode to its flag. attempts counts our solver runs.

mode work to flag attempts wrong submits
single 1.8s 1 0
time trial 1.2s 1 0
mastery 4.4s 1 0

the clock

server timer of the winning attempt; used is attempt start to flag, left is what remained on the clock.

mode time available time used time left
time trial 50.0s 1.2s 48.8s
mastery 410.0s 4.4s 405.6s

where we got stuck

flags: single, time trial, and mastery [redacted].

{generated by a clanker}