hmx78912 on 2025-06-29 04:41:
Also forgot to add: No PATCHING aloud.
GOAL: FIND PASSWORD
nightxyz on 2025-06-29 07:02:
I guess I'll make you angry again but this one didn't even take 10 minutes to crack. After seeing the part that checks the length of the password to 10 characters, I entered a random password. After the size check, after a few more steps, x64dbg showed a string as "awesome". I didn't even look at the memory area. I tried that and it worked. The previous crackme was harder in my opinion. If the password in the previous crackme file had been encrypted, my job would have been harder. The plus of this was that while debugging this, if I wanted to run another program directly, the debugger would detect it and the program would exit. And it wasn't even running under the debugger. Your obfuscated codes are very similar to the programs written by "nado" called "watermelon crackme" and "professional crackme", but I haven't been able to crack them yet. There is too much math and obfuscated code.
hmx78912 on 2025-06-29 19:00:
Hmmm, lol. I guess i just have to accept defeat. but i will try figure out on how to properly encrypt the password, maybe copy others code , on the encryption side of things. :D
kalillisboa on 2025-06-29 22:44:
[Click to reveal]No clue if debugging was off-limits, but I noped the debugger check and flipped a few conditionals till it dropped “awesome123”
Coder_90 on 2025-08-09 17:30:
[Click to reveal]admin
123456 :))
Coder_90 on 2025-08-09 18:08:
[Click to reveal]awesome123 is the password :)