Number of crackmes:
Number of writeups:
Comments:
| Name | Author | Language | Arch | Difficulty | Quality | Platform | Date | Downloads | Writeups | Comments |
|---|
| Crackme | Date | Infos |
|---|---|---|
| Monster CrackMe 1.0 (MCM) | 2026-02-10 09:45 | nice crackme, you could split one key constant between parent and child and randomize small vm constants per run to make it harder. |
| Continental | 2026-02-09 19:12 | the main weakness is the hash compression step caused by left shift then byte truncation. if uniqueness is desired, avoid lossy truncation in the core check path. |
| Gadget | 2026-02-09 18:58 | |
| Find the serial key 2 | 2026-02-01 16:42 | |
| Prometheus 12 Levels of Madness | 2026-02-01 03:03 | !!wow |
| Custom Packer 2.0 | 2026-01-31 15:34 | keygen + writeup. cool |
| CrackMePlease | 2026-01-31 12:10 | |
| TryHard crackme with password | 2026-01-31 08:05 | |
| here no str? | 2026-01-29 21:58 | y0u_50lved_this_pr0blem |
| weird but easy | 2026-01-29 09:02 | cool |
| Religious entrance | 2026-01-01 14:11 | very fun ngl. |
| Last of 25 | 2026-01-01 12:37 | |
| Santa's Network Admin Portal (S.N.A.P.) | 2026-01-01 12:14 | |
| Insane Crackme - The Chaos VM | 2025-12-31 15:16 |
| Crackme | Comment | Date |
|---|---|---|
| Lugosi's CrackMe II | i am going to ask again if you can provide a valid name/serial pair. | 2026-02-11 21:19 |
| Impossible PatchingMe V2 | key: asd status: ok PAYLOAD: Q1ZNMQEAAACIl5al8OHSwwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHx+crcxMhU9pQjMy28xnumyj4kkbAbZJWXkIYec2tMkdjI7xE+PF+U78tves0+3ykGVwJokRo1gFr5Y33JU/DTYX5E0ZaiMSXsKdRqPSbKsHsAqHS/IvoWYozmMtlV9J6clR2dg9w0O5JCbgbWsK LEMAAAA892AW0RjL6FklaZsRAAAAOumlh+LIaY5becwYz0jFdLKs8C0a1Ygki87JdxIVSzWhC2paysREdtsqcBpNaUx+gmITBGQy4gJ5FZr5RfEh0OfCV1DGAAAAAD/QJjtdgd3ZYIMAAAA2x8Bgnbo194AILnVIQAAAPgL9S0Cnlw5V8xkXSiYE9pFeq/H/6UMY3MnwuFQiFBqeAEAzM XYigGiIY0MAAAASWxIUzGZAohjoveYEgAAAI8+76wBT1dOSDLQqQV2B52wTwIAloxPg3pEI6oMAAAAxP81JdTx6vzFhcPSEgAAAIAQsESCNdmLNxRQIghmLI+VHwMB7ezXwDwWLqkMAAAAEdMQdG0GL9xNg8VCEgAAAIXLx8qzrobBerHcaFlCLzORTwQDkLBndIOre3kMAAAAeLsyx8e 6DNsCye5REgAAALJU9oIvfNtqyrn2x87316Zi+wUETQwPA8yqwt4MAAAAX89h1XAzhH9FLTzaEgAAAHkLPXoxI1z3G4IFL009JEvfqAYFMGv0Y4OViy4MAAAAaQ5oT1hPDV4QYb6tEgAAAJFjcmvOazWOc+ea9viF3gkehgcG3MzybsKXOUsMAAAAnJI5jHvsZhcJgPg1EgAAANzBrUFd 6Oc2ML4P22G7u6KdZwgHK3UgfmwvUdgMAAAAJJUVoZGoykN+2dejEgAAABaCx/22Q0KHI0WSPlfGD675ygkI8cucf4OWGjEMAAAAtYyMUIbDIrbfDcw8EgAAAJtH8qoZ3WGX5UHVMPEqRH7o2QoJyxrVvvHGp5EMAAAAjnxdkp6Fe9eYyStgEgAAAHSoMIrnPwA4i/TEPljG1QhjIgsK1 GCQKTz4h5wMAAAApr+f0IDt9EHMFAtaEgAAAMT6oKnauwwSXAj4iurN+c+KlQwLrlsrEKVNEscMAAAAoPmAawk6P+ytbL/lEgAAAG7M98uIQPndvPuucic+GGRw1Q0MOye62O0UIl8MAAAABMo9hMlMyLVVpbc7EgAAAIBDQTOsRVfOcSo1A4kog3t0Rw4NgATaFGgEQssMAAAABrkOqh oj8/Fh/zwUEgAAAKRWCvWOfAY1YHqcv4bT6vNFXA8OYpcR6aGZXrIMAAAAou0bHXYCcP1Oda6zEgAAAMEbmEJHrbkBc6RROOms3yfn/BAPPHp+uD0Fj/UMAAAAfh9ozq+d0WAU3NIqEgAAAIOsF+BevptAjC/KJ6bAqULqzxEQm97lECSQ1KkMAAAAwXRrowTsCkvIw2c+EgAAALPoV4P U3Na23wYJ0Vi4+cHlLBIRQ3Fe07B1GgMMAAAAi+/vmvAilXSN9YfwEgAAAGomoZF0Rovja0NSpqj1HB3O3BcSMw8SUEn/glYMAAAAsj3t2hdkhW5+Q7aMEQAAAO/HChNy9yxhIMUmXa+dnjDMEwIEy8d5MPQrhQwAAABVPJEJJb0v0CAK9RQSAAAAz7Vu77foUJQe+cVM8xU2RZ0bFBPB A3zMkmtDdQwAAAAQ2V83qXnS+fkngOMSAAAAMTqvgWoF1Sso4Ii4GWE+t/k3FRQTo5MILTMLmAwAAAAe3iFgr40QOc5nNIcSAAAAG7DPdGB3zXTi22tFa4ye2DNLFhV1G3LSX6MeGQwAAAAX9cYcormGhDTMrx0RAAAAtOBs7e+XQS4gHmNwV43c+gU= | 2026-02-11 20:59 |
| Impossible PatchingMe V2 | patch 1 va 0x1400022cb old bytes --> 84 c0 new bytes --> b0 01 this makes status always ok for any input after that patch, the program reaches success path. but payload can appear blank so we patch the payload pointer patch 2 va 0x140002372 old rel32 --> d6 84 05 00 new rel32 --> 3a 85 05 00 this changes lea rdx, [rip + disp32] to point at the long payload blob at 0x14005a8b0 | 2026-02-11 20:56 |
| Impossible PatchingMe V2 | i dont understand... getting the software to print status ok is a matter of doing 2 patches | 2026-02-11 20:54 |
| Lugosi's CrackMe II | nevermind... i can kinda force "OK" but my method needs still some serious work | 2026-02-10 10:46 |
| Lugosi's CrackMe II | can you provide a valid name/serial pair? this crack me appears mathematically unsatisfiable/impossible to solve. | 2026-02-10 09:20 |
| Continental | dm me on discord if you want some help (@djd320) | 2026-02-10 06:22 |
| Find the correct key! | after some static analysis im now even more confident its legit | 2026-02-02 20:46 |
| Find the correct key! | I am pretty sure it is not malware. check-keys.exe is UPX packed and likely triggered the detection. | 2026-02-02 20:37 |
| Froggy CracMe | Name / Handle: djd320 Serial: 6579BE7D-A0DBF5E5-4C6D8825-426C0AAE | 2026-02-02 19:13 |
| TryHard crackme with password | there's a fundamental flaw cause the password is embedded in .rdata (ascii+utf32) and the character checks read it directly, so the vm/hash layers are mostly decorative. writeup coming soon. | 2026-01-31 08:01 |
| weird but easy | this is probably a 3.5-4.5 id say. for sure not a 2 | 2026-01-31 07:08 |