TCS HackQuest Season 11 – Practice & PYQ

TCS HackQuest Season 10 — Round 1 Walkthrough (Q1–Q5)

Detailed problem breakdowns, underlying security concepts, commands, and flag extraction steps for the first five Round 1 challenges.

Contest TCS HackQuest S10
Round Round 1 CTF
Questions Covered Challenges 1 to 5
Flag Format HQX{…}

Early challenges in TCS HackQuest Round 1 are designed to build momentum and test core foundational habits: reading file extensions critically, checking hidden strings or bit layers, observing application prompts, and tracing web flows. Below is a detailed walkthrough of the first five challenges with the reasoning behind each step.

1. Area 64

Encoding vs. Encryption

Problem Overview: You receive a compressed ZIP archive containing a text file with a short note and an encoded string. The challenge title (“Area 64”) hints directly at Base64 encoding.

  1. Extract the Archive: Unzip the downloaded file and open the text file inside to inspect both the message and the encoded block.
  2. Recognize Base64 Structure: Notice that the payload uses standard Base64 characters (A–Z, a–z, 0–9, +, /, and optional = padding at the end). Encoding transforms data representation—unlike encryption, it requires no secret key.
  3. Decode the String: Pass the extracted string into a Base64 decoder using a terminal command, Python, or CyberChef (From Base64).
  4. Extract the Flag: Read the decoded plain-text sentence to get the HQX{...} flag.
echo “<encoded_base64_string>” | base64 -d
Key Takeaway: Always distinguish encoding (Base64, Hex, URL encoding) from encryption/hashing before attempting brute-force or cryptographic attacks.
Flag: HQX{70c5d525cae36f419aa5b6a49bf4ccf8}

2. NOISE

Static File & String Analysis

Problem Overview: You are given a file with a non-standard .opt extension (56a6f5e0f.opt). Unfamiliar extensions often hold raw bytes, logs, or mixed binary data where printable text is buried amid noise.

  1. Check File Type & Extract Strings: Run the strings utility to scan the file for contiguous sequences of printable ASCII characters and save the output to a text file so you can search it easily.
  2. Search for the Flag Prefix: Since HackQuest flags start with HQX{, filter the dumped text with grep instead of scrolling through every line manually.
file 56a6f5e0f.opt
strings 56a6f5e0f.opt > output.txt
grep “HQX{” output.txt
Key Takeaway: Do not judge a file by its extension alone. Pairing strings with grep is one of the fastest ways to spot plaintext secrets or flag patterns in binary blobs.
Flag: HQX{543c40987ff16e08b6050b3649428016}

3. Hidden Layers

LSB Steganography

Problem Overview: Extracting the ZIP archive produces an image file. Rather than hiding text in plain sight or file metadata, the challenge points toward concealing information inside the image’s pixel bit-planes (Least Significant Bit / LSB steganography).

  1. Unzip & Load the Image: Extract the image from the archive and load it into CyberChef (or an LSB extraction tool).
  2. Configure LSB Extraction: Select Extract LSB, target the R, G, B color channels, and set the bit index to 0 (the least significant bit, where subtle bit changes are least noticeable visually).
  3. Inspect the Decoded Output: Check the beginning of the extracted data stream—the flag appears right at the start of the decoded output.
Key Takeaway: In image steganography challenges, try standard LSB settings (bit 0 across RGB channels) first; if the output looks shifted or noisy, check bit order, endianness, or alpha/channel combinations.
Flag: HQX{24c0ce09e04eedd63f11f1439d1d48f0}

4. StackFall

Input Bounds & Memory Leak

Problem Overview: The challenge exposes an interactive web terminal with a health> prompt. Normal diagnostic inputs behave predictably, while responses drop hints suggesting you “poke the stack.”

  1. Baseline the Prompt: Test standard inputs like ping or status to observe normal application responses and error handling.
  2. Interpret the Hint: A hint to “poke the stack” indicates potential memory-handling or buffer/length validation weaknesses when unexpected input sizes are supplied.
  3. Submit a Long Input Payload: Send an overly long string of characters into the prompt so the program’s input buffer or memory layout is stressed.
  4. Read the Leaked Output: Examine the response returned after the oversized input—the flag is exposed directly in the leaked memory output.
# Example quick payload generator (prints 500 ‘A’s to paste or send)
python3 -c “print(‘A’ * 500)”
Key Takeaway: Whenever an interactive prompt hints at stack or buffer behavior, test boundary conditions and long inputs carefully—unbounded reads or writes can leak adjacent data in memory.
Flag: HQX{8d0b49450b73c52f7569c2772b8e19b}

5. Chat Ops

Conversational Clues & Hidden Routes

Problem Overview: You interact with a ChatOps bot named Sentra. Asking directly for credentials or login details does not hand over a password; instead, the bot nudges you toward unlocking access and inspecting application paths.

  1. Engage Sentra & Collect Clues: Ask how to log in or gain access, and pay close attention to recurring themes in Sentra’s replies—such as admin access, unlocking, and a magic word/phrase.
  2. Trigger the Unlock Condition: Follow the workflow/hints in the chat so the application state or unlock logic is satisfied rather than expecting the chat bot itself to log you in.
  3. Navigate to the Admin Endpoint: Update the browser URL to the revealed admin login route pattern (/login-XXXX).
  4. Capture the Flag: On the Administrator page (with the user prefilled as Administrator and auth initialization logs visible), copy the flag displayed on screen.
Key Takeaway: In chatbot and web-logic CTFs, treat bot replies as behavioral signposts. Combine chat clues with URL/path inspection and browser DevTools when needed.
Flag: HQX{07acc3d5c163dbb87ce5b0ebf2bdf2fc}