h4ckc0n 2026 writeup (whoami)

Part of my h4ckc0n 2026 writeups. I played solo and finished first.


Still can't solve this challenge?
I gave Arjun his badge. I gave him his credentials.
I gave you every instruction Kabir provided.
Every file. Every hint. Every piece of evidence you needed was right there in front of you.
And yet, you still haven't solved it.
Don't guess. Investigate.
You've already solved the previous challenges - or at least, you thought you did. Go back. Retrace your steps.
Question your conclusions. Lookk closer.
You think I'm wrong? Prove it.
The answers were never missing.
You just haven't found them yet.
Flag format: d4rk{fragment1_fragment2_fragment3}
Each fragment may contain multiple words.
Separate words with each fragment using underscores.
fragment two is a name like: full_name guess who is the echo
For fragment3 - just find another one of echo's account on real social media, who could echo be obviously following? and who could be obviously following echo?

WhoAmI is the last part of the six-part Mirror Investigation story series. It came out in the last wave, about three and a half hours before the end. I solved it at 14:56 UTC, about half an hour before the event closed, as the fourth of nine solvers.

Flag: d4rk{author_tarun_yadav_is_the_hacker_you_are_looking_for_what_you_guessed}


The series so far

A crypto exchange is robbed at 3:14 AM, and you play Agent Arjun Mehra.

  1. The Setup: decrypting a message gives the investigation login a.mehraCC704 / drower4648.
  2. Digital Footprints: a netcat "investigation terminal". You log in, search a large evidence archive, and submit the true incident chain.
  3. Hidden In Plain Sight: a PNG whose pen strokes spell FEDIVERSE.
  4. Chasing Shadows: the fediverse leads to Arjun's Mastodon account, where the edit history of one post says github: ECHO-704. The commits of that GitHub account hide a sequence of numbers. The challenge text asks "who the hell is Echo? I need a name. An identity."
  5. Behind The Login: a web login that needs numbers from ECHO-704's commits.

Fragment 1: author

The Digital Footprints terminal uses this prompt:

NHGUBE:NovaVault>

NHGUBE is the only encoded token in about 20 MB of terminal output, and the challenge never uses it. ROT13(NHGUBE) = AUTHOR. The title WhoAmI is the shell command that prints the current user, and the user comes first in a prompt like this one. So the user of this terminal is the author.

A dead end

Two earlier parts also had a planted detail that their own solutions never used:

  • The Setup: the password drower4648. drower reversed is reword, which fits a series called Mirror.
  • Hidden In Plain Sight: the PNG's EXIF says Artist: d4rkc0de, right next to "nothing is inside this challenge".

These gave neat flags that were all rejected: d4rk{reword_author_d4rkc0de}, d4rk{reword_author_tarun_yadav}, d4rk{reword_author_thank_you} and others. After four rejections with the same reword_author prefix, I asked the author.

Asking the author

Tarun, the author, answered in tickets:

  • Fragment 1: author is right, and it comes from challenge 2 (Digital Footprints).
  • Fragment 2: "a name, think who the echo is".
  • Fragment 3: "sorry for that but there is glitch from my side / Updating you very soon".

The third answer explained why all my earlier guesses had failed: fragment 3 could not be found yet. I stopped submitting and waited for the fix. The description was then updated to say that fragment two "is a name like: full_name guess who is the echo".

Fragment 2: tarun_yadav

Who is Echo? The ECHO-704 GitHub repository from Chasing Shadows has two traces:

  • its commits are authored as ECHO with the author's own email address
  • its only pull request came from the fork tarunyadav-dev/-, opened by Tarun Yadav

Chasing Shadows asks for "a name. An identity.", but its flag was only numbers, so this identity was still unused. As full_name, it gives tarun_yadav.

Fragment 3: is_the_hacker_you_are_looking_for_what_you_guessed

After the fix, the author pointed me to Instagram and told me to read the description again. I went through the accounts that the organizer club's Instagram (@darkcode_iiitd) follows. One of them is the author's account, @with_tarunyadav, which has a post with this caption:

Here is fragment3: is_the_hacker_you_are_looking_for_what_you_guessed

Flag

d4rk{author_tarun_yadav_is_the_hacker_you_are_looking_for_what_you_guessed}

Read as a sentence: author Tarun Yadav is the hacker you are looking for, what you guessed. The answer to "WhoAmI" is the author's own name.

Lessons

  • When a multi-part flag keeps failing, check each part separately. One short ticket confirmed fragment 1, pointed me to the right source for fragment 2, and showed that fragment 3 was broken on the author's side.
  • Unused identities are planted. The Git author name in Chasing Shadows had no use in that challenge. In a story series, that means it is needed later.
  • The story can reach outside the challenge files. The last fragment was on the author's social media, found through the organizers' own accounts.

More from this event: recap · WhoAmI · h4ckmarket