Number of crackmes:
Number of writeups:
Comments:
| Name | Author | Language | Arch | Difficulty | Quality | Platform | Date | Writeups | Comments |
|---|---|---|---|---|---|---|---|---|---|
| KeygenMe(Second)_SWD | SirWardrake | C/C++ | x86-64 | 4.0 | 5.0 | Windows | 3:55 AM 03/04/2024 | 2 | 10 |
| KeygenMe_SWD | SirWardrake | .NET | x86-64 | 3.0 | 3.4 | Windows | 1:23 AM 02/28/2024 | 1 | 10 |
| Crackme | Date | Infos |
|---|
| Comment | Date | Link |
|---|---|---|
| Very nice crackme. Well done The password is really without fantasy^^ Spoiler: PW is 20 chars long and begins with "__" and ends with "rr" ;-) | 1:56 AM 01/31/2025 | ==> |
| 123 test test ;-) | 12:36 AM 12/23/2024 | ==> |
| nice and easy Another pw: $viM | 12:54 AM 11/26/2024 | ==> |
| since the password is in plain text, Xor encryption is pointless | 12:51 AM 11/05/2024 | ==> |
| Why do people post solutions that are obviously wrong? It would have been easy to check them... Congratz potichek, your solution is correct ;-) | 1:02 AM 07/29/2024 | ==> |
| Really, really easy... Come on, you could do better. | 12:09 AM 07/18/2024 | ==> |
| Real nice crackme with some obfuscation and anti-debugging. Had fun making a keygen | 1:39 AM 05/30/2024 | ==> |
| Very nice one. Had a lot of fun. Made a little keygen... | 2:02 AM 05/26/2024 | ==> |
| Very easy. I don't think the behavior was planned that way. Probably used "=" instead of "+=" by mistake. | 1:25 AM 05/24/2024 | ==> |
| extremely easy | 1:35 AM 05/23/2024 | ==> |
| Very easy. Just some simple math... | 1:19 AM 05/23/2024 | ==> |
| nice challenge. Wrote a little keygen 474-616889418 124-324579122 | 12:49 AM 05/22/2024 | ==> |
| Nice and straightforward crackme. Wrote a little keygen | 2:04 AM 05/21/2024 | ==> |
| Very nice one. I'm glad robot is happy now ;-) | 12:13 AM 05/19/2024 | ==> |
| Nice one. Some xor-fun. | 1:01 AM 05/17/2024 | ==> |
| Nice crackme. Very easy. | 12:13 AM 05/17/2024 | ==> |
| Oh damn, forget it. It's not a duplicate. Somehow my files are messed up | 11:55 PM 05/16/2024 | ==> |
| lol, this is a copy of "find a real key" by f0rizen... Better learn to code, and create your own crackmes | 11:50 PM 05/16/2024 | ==> |
| good one | 1:53 AM 05/16/2024 | ==> |
| Super easy. Password in plain text... | 1:15 AM 05/16/2024 | ==> |
| @alxxx: Nope, wrong password ;-) Extremely easy crackme. | 12:59 AM 05/16/2024 | ==> |
| Nice crackme. Wrote a little keygen... | 1:07 AM 05/14/2024 | ==> |
| Nice keygen. Wrote a little keygen... | 1:06 AM 05/14/2024 | ==> |
| it would be better to query the filename without the path. Otherwise quiet nice | 12:18 AM 05/14/2024 | ==> |
| Really nice. Made a little keygen | 2:18 AM 05/13/2024 | ==> |
| Nice and easy. Made a little keygen | 1:35 AM 05/11/2024 | ==> |
| Good job, very nice one. Valid key (there are many valid keys): 222p22=p222p22=p | 12:11 AM 05/10/2024 | ==> |
| Easy. The password is hardcoded, but "xor 5"-encrpyted ;-) | 10:22 PM 05/09/2024 | ==> |
| Very basic | 12:08 AM 05/08/2024 | ==> |
| DLLs can be found in MinGW/bin. The solution is way too easy. This should be difficulty 1.0 | 11:18 PM 05/06/2024 | ==> |
| Missing DLLs libstdc++-6.dll & libgcc_s_dw2-1.dll (can be found in MinGW/bin) Otherwise very, very simple to get the secret key | 11:11 PM 05/06/2024 | ==> |
| uses unknown versions of the MinGW-libraries. Better link them to the binary | 11:03 PM 05/06/2024 | ==> |
| Nice and easy. Uses some anti-debugging techniques. The password is easy to find (compares user-input with ascii) PW starts with "M" and ends with "N" ;-) | 12:31 AM 04/28/2024 | ==> |
| Finding out the password is very beginner-friendly | 2:14 PM 04/22/2024 | ==> |
| Very nice crackme. Lots of unnecessary code that helps disguise the password. Well done | 12:49 AM 04/22/2024 | ==> |
| Very, very simple. Keygen is not worth it | 1:16 AM 04/15/2024 | ==> |
| license key in plain text in source... I'll better try the VMP version | 12:05 AM 04/15/2024 | ==> |
| Extremely simple. Solved in less than a minute | 10:35 PM 04/14/2024 | ==> |
| hm, it won't let me post the c++ code properly | 1:53 AM 03/26/2024 | ==> |
| for (int i = 0; i 2) + ((2 * userIN[i]++) 2) + 56); | 1:51 AM 03/26/2024 | ==> |
| Really, really easy... Keygen: for (int i = 0; i 2) + ((2 * userIN[i]++) 2) + 56); | 1:50 AM 03/26/2024 | ==> |
| Very nice crackme! Easy to crack & easy to find a valid user-password-combination. But it was a bit difficult to find the function for the password calculation. However, now my keygen works... | 1:57 AM 03/22/2024 | ==> |
| @a764934018@outlook.com: Good job, that solution works well! Did you use Ida / Ghidra for this? | 1:05 AM 03/17/2024 | ==> |
| @cnathansmith Thank you for your support. I will dig into this approach. I think, I will stick with C++ for the time being until I am more familiar with the subject matter. | 8:49 PM 03/06/2024 | ==> |
| Nice one, not too hard | 8:38 PM 03/06/2024 | ==> |
| Damn it. I tested with dnSpy, it didn't give me the code. With ILSpy it's an easy task. After some research I found out, that I could use a packer and obfuscator to hide the code. BUT I also learned, that nearly all of them could be bypassed in seconds. So, is there a way to obfuscate the C#-code properly? Or is it all snake-oil and it's best to NOT use C# for crackmes? | 4:08 PM 03/04/2024 | ==> |
| Very easy. Nice idea | 1:57 AM 02/27/2024 | ==> |
| Nice and easy | 2:42 AM 02/26/2024 | ==> |
| This is the mother of all Anti-Debugging Code^^ After fixing this problem, the password-scrambling-part is easy to solve. Made a little keygen... Nice one!! | 12:48 AM 02/22/2024 | ==> |