Number of crackmes:
Number of writeups:
Comments:
| Name | Author | Language | Arch | Difficulty | Quality | Platform | Date | Downloads | Writeups | Comments |
|---|
| Crackme | Date | Infos | Actions |
|---|
| Crackme | Comment | Date |
|---|---|---|
| DPRK Loyalty Evaluation | My songbun is now the highest possible | 2026-07-21 17:41 |
| FRONTLINES | This one took me a bit! Rust seems to add so much more noise than I'm familiar with. The LIONOFJUDAH remains undefeated. | 2026-07-21 16:09 |
| Where is the challange? | [Click to reveal]Thanks! abc123!! | 2026-07-17 00:38 |
| ZEXOR-v1(Linux version) | [Click to reveal]AEXORRBSHA36325S33 | 2026-07-14 00:08 |
| Keygen-Me | [Click to reveal]You are him! Cybersphere{Speed... | 2026-07-13 17:05 |
| Level 9 | Found this one too. Thanks for uploading these! I'm saving these for educational purposes. They are a nice incremental exercise in complexity. | 2026-07-13 01:03 |
| Level 8 | Welcome to the matrix! | 2026-07-13 00:54 |
| Level 7 | Thanks! found the license ;) | 2026-07-13 00:52 |
| Level 5 | 6052 / 1213 Victory! | 2026-07-11 15:21 |
| Level 3 | thanks! | 2026-07-11 15:11 |
| Level 2 | [Click to reveal]Thanks! I was able to reverse this one with 5Ah | 2026-07-10 22:11 |
| Level 1 | Thanks! I found the password | 2026-07-10 21:26 |
| very simple login | Thanks! This one was fun figuring out the transformations making the password! | 2026-07-09 15:00 |
| karity-crackme-A | [Click to reveal]KARITY{my-first-crackme-here} | 2026-07-09 03:30 |
| c++ crackme 6/10 | [Click to reveal]It seems there are several serial options that work, serial_[E69r works for example. | 2026-07-09 02:49 |
| Secret key | Thanks! I'm very much a beginner, and these are great practice. | 2026-07-09 02:06 |
| Easy Crackme For Beginners | [Click to reveal] I recovered a VM-accepted key: '#P*AAAAAAAAAAAAAAAAAAA But when the program is run normally on my Windows VM, it does not print [+] helal bro.. It crashes first. The issue is in the custom VM. For any 23-byte input, the doubly decoded VM bytecode begins with: 01 fe xx xx xx xx That dispatches to the VM “load immediate” handler and executes effectively: mov dword ptr [vm_state + 0xfe * 4], imm32 In my crash dump, this faulted at: RIP: 0x422555 Instruction: mov dword ptr [rax+rdx*4], ecx RAX: 0x006ffd90 ; vm_state RDX: 0xfe Target address: 0x00700188 StackBase: 0x00700000 Exception: C0000005_ACCESS_VIOLATION So the VM writes far outside its intended state/register area. On this environment, that lands just above the thread stack and hits unmapped memory before the success branch can print. To prove the key path, I did not patch the executable. I launched the original program suspended, reserved the page above the child thread’s stack with VirtualAllocEx, then resumed it. With that page mapped, the same key reaches the VM halt path and prints: [+] helal bro. So the key logic is recoverable, but normal execution is blocked by an out-of-bounds VM state write that appears to depend on stack layout. Unless this is some trap setup and I'm falling for it! | 2026-06-26 01:51 |
| Easy Crackme For Beginners | Actually, i don't think its right. Disregard!~ I'm unable to delete my previous comment. | 2026-06-26 01:39 |
| Easy Crackme For Beginners | [Click to reveal]'#P*AAAAAAAAAAAAAAAAAAA | 2026-06-26 01:34 |