Author: pattu_sai
Listen to the music and chill https://open.spotify.com/track/2Okgqrcl83f9ZDQ5ZZK3jb
IT’s NOT THE SAME WHAT YOU SEE WITH UR EYES.
ENC FLAG MD5 : 7b757b8049a319a68888c93c53315b16
You were given pseudo for the “pseudocode” of the challenge and flag.enc containing the encrypted data. (it was pretty much just the actual code though)
| |
(this was the “fixed” handout, the previous one leaked len(data) as 0x32b7 and also had infile="flag.zip" 💀)
| |
Reconstructing The Image#
It is not difficult to see the PNG header 0x89 0x50 0x4e 0x47 being formed on reversing the pseudocode
Let’s get the image back
| |
giving us the image

O7EDJ{Wdhi_89k25397ewsm5?40o594307j71s3sh4e}
Missing Character#
In the image you can see there’s one character that’s not entirely visible, we can just bruteforce it and compare it to the hash given to us in the description
| |
Decryption#
After this we tried every possible encoding/decoding we could think of to no avail. I finally raised a ticket asking to confirm if the flag was encrypted or encoded and the challenge author said it was properly encrypted with a key.
Immediately we tried the Vigenere cipher and tried the guess the key to recreate the flag format
We got the key HCKERS and the flag:

H7CTF{Flag_89a25397afaf5a40e594307f71b3aa4c}
