Upload:
9:20 AM 08/30/2025
Description
Try to patch, should be not so hard, also you can find password very easily, if you have eyes :)
Ur main goal is patch.
Also feel free to give a feed back about the protection, i would like to read and improve.
The source code of the protection - https://github.com/generin0/PatchGuard
The source code of the crackme - https://github.com/generin0/crackme1
You must be logged in to post a comment
mxo on 11:09 AM 09/01/2025: * Can be found statically if you know how the key is obfuscated.
* OR when debugging, identify the CRC check and NOP it
* OR (easy way) Run till it asks for key, then dump from memory :)
kiokko89 on 6:45 PM 09/01/2025: my first crackme! i patched the call to "createthread" so the integrity check doesn't start
iwannabecoder on 7:37 PM 09/14/2025: i dont know how to solve this its too hard
my discord : zhqa_
Zailox on 8:25 PM 09/16/2025: Changing jne jumps to "Wrong key" to jmp`s to "Welcome" is considered a successful patch? It's okay to look for the key, but why try to bypass something for a simple patch?
genass3 on 12:05 AM 09/18/2025: Zailox, yes it counts as a successful patch, but this crackme wasnt suppose to be hard, i just wanted to test my patch protect a little bit, i wanted to weed out easy methods of bypass or make them more difficult to use, thats the reason i made a v2
bytehandler on 11:54 PM 09/18/2025: [SPOILER AT THE END]
The anti-patch was easy to bypass. I just attached a debugger and stepped over the entire PatchGuard init check. Once that's bypassed you can do anything. Great work on the static puzzle! I decoded the key by taking the little-endian bytes of 0x50475550475547, XOR-ing the 16-bit pairs at offsets 1, 3, 5 with 0x3333, and setting the first byte to 0x74 ('t'), which revealed the key: tftcftc
genass3 on 1:22 AM 09/19/2025: @bytehandler: Thx for your explanation, it would be helpful for beginners
PL45M4 on 8:20 PM 10/03/2025: Here is my writeup on this crackme: https://bobbyhillreverseengineering.blogspot.com/2025/10/crackme-genass3s-patch-protect.html
Thank you genass3 for the challenge. I left a little note at the end for you. You may have already implemented those suggestions in your V2.
genass3 on 6:12 AM 10/04/2025: @PL45M4: Yes i did implement most of ur recommendations in v2, but i forgot to crypt some of strings unfortunately, btw nice writeup!
You must be logged in to submit a writeup