big entrance: the other byte order

huntress ctf 2026, day 20 · warmups · all three modes

tools used: decoding search engine and timed-attempt pipeline.

the prompt: "same bar. this time the big one goes first." day 19's blob was hex of utf-16 text behind the little-endian byte-order mark; day 20's is hex of utf-16 big-endian text behind fe ff. the single and the time trial were one such hex line each; the mastery was a zip of 98 blobs of twenty numbered lines, each line under its own day's encoding, the twentieth in the day's new form.

the key insight: a byte-order mark says which order the text is in, so a reader that honours the mark reads both days with the same code. the day's work was naming the new order in the line schedule so the next day's line is the only unknown.

challenge shape

single        1 field    one hex blob, the whole message
time trial    1 field    one hex blob, fresh text
mastery      98 fields   98 blobs of 20 numbered lines, line k in day k's form

the field is message (setK.message in mastery): the slug the final decoded line names.

artifact anatomy

the single's blob, and the mastery's line 20, is lowercase hex. decoded, it starts with fe ff and then the zero byte comes first in every pair: utf-16 big-endian with its mark. day 19's line 19 decoded to ff fe and the zeros on the other side.

extraction method

every reading in our decoding engine turns bytes into text through one function that checks a byte-order mark of either order before it tries utf-8 (the day 19 fix), so the plain hex step already read the single and the time trial. the line schedule (line k by day k's encoding) read the mastery's lines 1 to 19 by their rows and searched line 20; the search found hex and the text reader did the rest.

raw = bytes.fromhex(line)
if raw[:2] in (b"\xff\xfe", b"\xfe\xff"):
    text = raw.decode("utf-16")      # the mark picks the order
elif not any(raw[0::2]):
    text = raw.decode("utf-16-be")   # no mark: the zero byte leads each pair

validation and answer formatting

the slug shape the question states ("three lowercase words separated by hyphens, followed by a hyphen and a two-digit number; submit the slug only") decides which reading is the message; a reading that is not a dictionary slug is reported, never submitted.

failed approaches and pivots

none on the day. after it we found the schedule had recorded line 20 as plain hex, which is true but loses the order: a reader that refuses the little-endian order (utf16behex) is now row 20, and the big-endian words (big one, big-endian, big entrance) hint it, so a day-21 prompt that says "big" tries that order first.

automation across modes

the same engine reads the single, the fresh time-trial blob and all 98 mastery blobs; in the mastery only a line past the schedule is searched.

lessons

solve times

public scoreboard · day 20 finish: below top 10

  • 0:02.0single#3 of 184 solvers
  • 0:03.3time trial#2 of 175 solvers
  • 0:05.1masteryfirst blood, +1.3 s
  • #25team day finishof 150 teams that cleared it, in 12:50.9
  • #1single 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.

mode work to flag attempts wrong submits
single 0.9s 1 0
time trial 0.7s 1 0
mastery 0.9s 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 30.0s 0.7s 29.3s
mastery 115.0s 0.9s 114.1s

where we got stuck

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

{generated by a clanker}