> For the complete documentation index, see [llms.txt](https://everythingblackkk.gitbook.io/everythingblackkk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everythingblackkk.gitbook.io/everythingblackkk/ctf/eycc-2025-forensics.md).
# EYCC 2025 - Forensics
Hello everyone,\
This challenge is considered medium-level, not too difficult, but it contains some combined ideas which made it quite interesting.\
Let’s talk about the beginning.
In this challenge, we have a **ZIP file**.
```
- file CUNTISSIMO.zip
CUNTISSIMO.zip: Zip archive data, at least v5.1 to extract, compression method=AES Encrypted
```
But it was protected with a password. At first, I used **rockyou** to try and crack the protection.
I used this code to do it, and indeed the password turned out to be **12345678** — much easier than I expected.\
That was actually quite funny.
```python
import pyzipper, sys
found_it = False
zf = pyzipper.AESZipFile(sys.argv[1])
for w in open(sys.argv[2], "rb"):
pw = w.strip()
try:
zf.extractall(pwd=pw)
print("\n\n[+] Password:", pw.decode(errors="ignore"))
print("\n\n")
found_it = True
sys.exit(0)
except:
continue
if not found_it:
print("[-] Not found")
```
Now we have a file, but it doesn’t open. At first, we tried using some tools, like **binwalk**, to extract files from it or something similar, but all attempts failed.
However, we noticed something very important: when we looked at the **hex** using
```
hexdump -C TARGET
```
we found data indicating the presence of a **JPEG**, but the first 3 bytes in the hex were essentially corrupted.
So, we searched for the correct **magic number** in a GitHub repo, and the expected result was:
```
ff d8 ff e0
```
***
Now I opened the site [**https://hexed.it/**](https://hexed.it/) so I could edit the first 3 bytes and change them to the correct value. After doing that, I clicked **export**, and here came the surprise!
An image appeared that contained some encryption, and I thought it was the **flag**.\
At first, I assumed it was **Base64**, but it wasn’t.
```
MYZWQMDYIRZGCY3VHBWGC5Y=
```
So I tried **Base32**, and indeed it revealed the flag!!!
```
eycc{f3h0xDracu8law}
```
***
## Thank you all! I hope you enjoyed the article. If you have any questions, I’m here to help.
Remember My name : everythingBlackkkMade
by ❤
Github :
Linkedin : [www.linkedin.com/in/everythingblackkk](http://www.linkedin.com/in/everythingblackkk)
X :
Youtube :
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://everythingblackkk.gitbook.io/everythingblackkk/ctf/eycc-2025-forensics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.