| Prometheus 12 Levels of Madness |
djd320 |
!!wow |
2026-02-01 03:03 |
View |
| TryHard crackme with password |
0xVoldeM0rt |
Happy To Reverse :) |
2026-01-31 03:46 |
View |
| CryMore |
EngineerShell |
- Execution required > Yes
- Payload extraction > Not required
- Dynamic analysis > Required
- Primary technique > Static analysis + Dynamic execution
- Key concept > KillSwitch mechanism (WannaCry inspired and my experience)
- Obfuscation type > None
- Risk level > Simulated Malware
- Tools used > Python 3, HTTP server, Linux/Parrot OS, Windows 11, Detect it Easy, unzip, notepad++ |
2026-01-31 01:59 |
View |
| Simple obfuscation |
stackpointer7 |
The file contains an overview of the program and code that generates the valid key! |
2026-01-29 00:17 |
View |
| Password And Flag in C |
svidnet |
Pretty basic and easy crackme.And write-up for it |
2026-01-28 15:46 |
View |
| Project Obscura |
ventie |
Operation Obscura by 0x3xp
1. Challenge Info
Filename: ProjectObscura.exe
Author: 0x3xp (Piyusha Akash)
Difficulty: 1.3/5.0 (Easy)
Architecture: x86-64
Language: C/C++
2. Protection Overview
The author mentioned that the flag and secret key are not stored in plain text. The binary utilizes:
TLS Callbacks: Used to execute anti-debugging or initialization code before the main Entry Point is reached.
Stack-string Reconstruction: Strings are built dynamically in memory during runtime to evade static analysis.
Junk Data: Misleading strings like Cr4ck_m3_... are present in memory to confuse the analyst.
3. Solution Process
Phase 1: Dynamic Analysis Setup
Load the binary into x64dbg.
Step through the TLS Callbacks (breakpoints triggered at 00007FF606D51D80 and 00007FF606D51D60) by pressing F9.
Continue until the debugger hits the actual Entry Point.
Phase 2: Identifying the Comparison Point
The program prompts for a secret code: :: Enter the secret code: . Since it needs to verify the input, it likely uses a string comparison function.
Set a breakpoint on the strcmp function located in ucrtbase.dll.
In the program console, enter any dummy text and press Enter.
Phase 3: Extracting the Secret Key
The debugger will trigger the breakpoint inside strcmp. Examine the registers:
RCX: Points to the user-provided dummy input.
RDX: Points to the actual reconstructed secret key required by the program.
Value in RDX: 0xP670PPGT56DEA.
While other obfuscated strings were visible in the memory dump, this specific value was the one used for the final validation.
4. Final Result
Restart the program and enter the discovered key: 0xP670PPGT56DEA.
The program triggers a message box: "Congratulations you found the Flag!".
Flag: CTF{R3v3rs3_EnG_1s_4M1ndG4m3s} |
2026-01-28 15:02 |
View |
| crackme2 by seveb |
dynaspinner64 |
Writeup for 64-bit version of crackme2. |
2026-01-26 17:04 |
View |
| easyAF |
b0bd0g |
Detailed walk through of the program flow and explanation as to why looking at high level disassembly is not sufficient and why we must analyze the raw assembly in order to find the answer. |
2026-01-26 02:50 |
View |
| BeginnerFriendly |
chikom35t |
Easy input validation crackme |
2026-01-26 01:45 |
View |
| crackme05 by seveb |
dynaspinner64 |
Writeup for the 64-bit version of crackme05. |
2026-01-25 08:51 |
View |
| Rev1 |
b0bd0g |
I believe this crackme is impossible without patching |
2026-01-24 13:50 |
View |
| CrackMe4 |
reqviums |
GUI crackme based on a name-dependent serial generation.
The serial is generated in two parts using a custom rolling hash algorithm.
full analysis in the attached text file |
2026-01-22 20:16 |
View |
| Happy New Year tiny puzzle with a twist |
Suicidee |
Execution required: No
Payload extraction: Not required
Dynamic analysis: Not needed
Primary technique: Static analysis
Key concept: Distinguishing displayed syntax from executed syntax
Obfuscation type: Symbolic / psychological misdirection
Risk level: Harmless (echo-only behavior)
Tools used: Text editor only |
2026-01-21 17:47 |
View |
| Easy crackme |
LogRob01 |
Java crackme solved using static analysis.
The JAR file was decompiled with CFR to analyze the validation logic.
No patching or keygen was used.
The solution is based on understanding the character-based validation conditions.
|
2026-01-17 22:18 |
View |
| crackme1 by seveb |
dynaspinner64 |
Writeup for the x64 version of crackme01. |
2026-01-17 07:31 |
View |
| ZEXOR-v1(Linux version) |
h4wtsauce |
writeup in Markdown for the ZEXOR v0.1 crackme challenge |
2026-01-16 10:41 |
View |
| Hacker's Edge Book CrackMe v2 |
msym |
The solution (the string that needs to be keyed in to solve this crackme) is redacted as the author provided a coupon code to to redeem his memoir for free. The coupon code is also redacted. |
2026-01-14 07:48 |
View |
| ZEXOR-v0.1 |
RemiAstera |
this is my first write up. |
2026-01-13 22:50 |
View |
| Azure |
msym |
I hope it is detailed enough. |
2026-01-12 14:36 |
View |
| Happy New Year tiny puzzle with a twist |
jeffli6789 |
Automated analysis with Claude code CLI |
2026-01-11 04:12 |
View |
| really easy |
tkhnnh |
A beginner-friendly guide |
2026-01-10 07:45 |
View |
| crack the key |
stackpointer7 |
This file contains a writeup of what the code does and generates the correct flag |
2026-01-07 19:32 |
View |
