← Back to Writeups
HTBN/AMisc

badyuri

XESXOR8/23/20263 min read
#misc#htb#n/a

badyuri

Platform: B01Lersc | Category: Misc | Type: Challenge | Difficulty: Easy | OS: NA | Author: D3v0o0Nu11 | Date: 2026-04-18 | Status: Solved Techniques: ascii_offset_decoding, character_substitution, unicode_codepoint_diff

Summary

Task: two near-identical UTF-8 text stories where 30 ASCII characters were replaced with higher Unicode code points, hiding data in the offsets. Solution: pair characters position-by-position and concatenate chr(ord(modified) - ord(original)) for each mismatch to recover the flag.

Recon

Port scan

nmap -p- -sV -sC <TARGET> --min-rate 1000 -Pn
PortServiceVersionNotes
<PORT><SVC><VER><notes>

Enumeration highlights

  • Event: b01lersc | ID: 20260418_b01lersc_badyuri
  • Tags: steganography, unicode, text, diff, ascii_offset
  • Indicators: two near-identical text files with tiny visual differences, ASCII letters replaced by Latin-1/extended Unicode characters (e.g. had -> haÆ, her -> hÈr), both files have the same Unicode code point count but different byte length, hint mentions 'find the difference between these two files
  • Source: 20260418_b01lersc_badyuri.md

Foothold

Vulnerability / Misconfiguration

  1. Ascii_offset_decoding
  2. Character_substitution
  3. Unicode_codepoint_diff
<command>

Exploitation

  • See original writeup content for detailed exploitation.

Privilege Escalation

Enumeration

sudo -l
find / -perm -4000 2>/dev/null
getcap -r / 2>/dev/null
cat /etc/crontab
ps aux

Exploitation

  1. N/A for challenge-type writeup; see exploitation above.
  2. Flag obtained via challenge solve.
<command>

Flags

FlagLocationValue
flagREDACTED

Key Takeaways / Lessons

  • ascii_offset_decoding
  • character_substitution
  • unicode_codepoint_diff
  • Tags: steganography, unicode, text, diff, ascii_offset

Original Writeup

<details><summary>Click to expand original content</summary>

Description

Corporate wants you to find the difference between these two files. They are not the same file.

Given: yuri.tar.gz containing yuri/yuri.txt and yuri/yuri_1.txt — two roughly 10 KB UTF-8 text stories that read identically to the eye but have slightly different byte sizes. The goal is to recover a hidden flag from the differences.

Analysis

After extracting the archive we have two files:

10249 bytes  yuri.txt     (original)
10273 bytes  yuri_1.txt   (modified, 24 bytes larger)

Both files have 197 lines and, crucially, the same number of Unicode code points (9907 each) — so the modification is a 1-to-1 character substitution, not an insertion. The byte-size difference comes purely from some of the modified characters now needing 2 UTF-8 bytes instead of 1.

Running diff shows exactly 30 lines where a single ASCII letter has been swapped for a visually similar but slightly different character from the Latin-1 / extended Unicode range:

< had their toys ...              -->  < haÆ their toys ...
< her friend ...                  -->  < hÈr friend ...
< Additionally ...                -->  < ¼dditionally ...
...

The replaced characters are always just above the ASCII range. That is the hint: the difference in code points is small and deterministic. For every mismatched pair (original, modified):

delta = ord(modified) - ord(original)

lies in the printable ASCII range [0x20, 0x7E]. So each substitution is encoding one byte of hidden data via the offset.

Solution

Walk both files character-by-character, compute the delta at every mismatch, and concatenate the results in reading order.

#!/usr/bin/env python3
# Recover the hidden flag from badyuri

with open('yuri/yuri.txt', encoding='utf-8') as f:
    orig = f.read()
with open('yuri/yuri_1.txt', encoding='utf-8') as f:
    mod = f.read()

assert len(orig) == len(mod), "Code point counts differ"

flag = ''.join(
    chr(ord(m) - ord(o))
    for o, m in zip(orig, mod)
    if o != m
)
print(flag)

Output:

bctf{REDACTED}

The 30 mismatched positions yield the 30-character flag, one ASCII character per substitution — a neat little Unicode stego channel.

</details>

Auto-tracked: saved to WriteUps; run /xesor-revise to fold lessons into XESXor_Methodology.md.

signed by XESXOR