OFFICIAL RAID WRITEUPS

Welcome to the official repository for challenge writeups for SEASIDES HACK QUEST'25 and IICON PURSUIT'25! This repository is dedicated to documenting solutions and methodologies used to solve challenges presented during these events.

Table of Contents

• Introduction
• Structure
• Contributing
• Code of Conduct
• License

---

Introduction

Defhawk RAIDs are premier cybersecurity challenge events, bringing together enthusiasts and professionals to solve a variety of challenges in domains such as:

• Reverse Engineering
• Secure Coding
• AI/ML
• Blockchain
• API Security
• Threat Research
• Threat Intel
• Exploitation
• Cryptography
• Web Security
• Forensics
• Miscellaneous

This repository serves as a centralized resource for:

• Detailed writeups of challenges.
• Insights into problem-solving techniques.
• Sharing knowledge and methodologies with the community.

---

Structure

The repository is organized as follows:

root/
├── SEASIDES_HACK_QUEST_25/
│   ├── Reverse_Engineering/
│   ├── Exploitation/
│   ├── Cryptography/
│   ├── Web_Security/
│   ├── Forensics/
│   └── Miscellaneous/
├── IICON_PURSUIT_25/
│   ├── Reverse_Engineering/
│   ├── Exploitation/
│   ├── Cryptography/
│   ├── Web_Security/
│   ├── Forensics/
│   └── Miscellaneous/
└── README.md

Each subdirectory corresponds to a challenge category. Inside each category folder, you will find:

• A separate folder for each challenge.
• A README.md file in each challenge folder containing the writeup.
• Supporting files such as scripts, payloads, and challenge binaries (if permissible).

---

Contributing

We welcome contributions from the community! If you'd like to add a writeup or improve existing ones, follow these steps:

1. Fork this repository.
2. Clone your fork to your local machine.
3. Create a new branch for your changes:

   git checkout -b my-challenge-writeup

4. Add your writeup and any supporting files.
5. Commit your changes with a descriptive message:

   git commit -m "Added writeup for [Challenge Name]"

6. Push your changes to your fork:

   git push origin my-challenge-writeup

7. Create a Pull Request to merge your changes into the main repository.

Guidelines

• Use clear and concise language.
• Include screenshots, code snippets, and explanations where applicable.
• Ensure all supporting files are properly sanitized and do not violate event rules.

---

Code of Conduct

We are committed to fostering an open and welcoming environment. By participating in this project, you agree to adhere to our Code of Conduct.

---

Happy hacking! 🚀