DEBUG THE DEAD

Murder Mystery Coding Event

General Guidelines:

  • Each team must consist of 2 members.
  • It will consist of 3 phases with a total time limit of 1 and half hour (or as per event structure).
  • Internet access is prohibited unless explicitly permitted by the organizers.
  • Use of any external programming scripts, tools, or pre-written code is strictly disallowed.
  • Each team will be assigned a designated table/workstation.
  • Participants must remain at their designated station throughout the event unless instructed otherwise.
  • Teams must work independently. Sharing solutions, hints, or code with other teams is strictly prohibited.
  • Respect for fellow participants and organizers is mandatory. Misconduct or disruptive behaviour will lead to disqualification.
  • The decision of the Judges will be final and binding.
Event Poster with vibrant colors and event details

Phase-Specific Rules

Phase 1: Hacked Server

Teams will receive a corrupted HTML/CSS file to debug. The corrected file must display the hidden web page link leading to the next phase. Only one submission per team is allowed for this phase, so review your work carefully before submitting.

Phase 2: Crypted Files

Teams must debug the given Python code to decrypt the files. The solution must correctly decrypt and display the chat logs for Phase 3. Teams may only use the debugging tools provided or those already installed on their laptops.

Phase 3: Leaked Chat Logs

Teams must decrypt and analyze the chat logs to deduce the culprit’s name. All answers and evidence must be compiled in a single final report for submission. The final answer (culprit’s name) must be accompanied by logical reasoning and proof derived from the logs.

Grounds for Disqualification