Profile

Crackme	Date	Infos
C++ idk	2025-12-25 20:55	Windows x86-64 C/C++ console crackme. Traced the password-handling path through std::string helpers in x64dbg and found that the apparent stack constant (`a#l67’gdb`) is a decoy; the real key is computed deeper in the transformation flow. Final password: `4v9cbr217`.
StaticAuth	2025-12-24 22:17	Windows x86-64 “authentication code” crackme solved via static analysis (Binary Ninja HLIL). Recovered the runtime-reconstructed password from lightly obfuscated embedded data; correct code is `goodjob123`.
Assembler Crackme	2025-12-21 02:27	x86 assembler crackme. Traced the password path from `ReadConsoleA` into the validation routine and identified an 8-byte memcmp-style loop against a static byte table. The correct password is the exact 8-byte sequence `@CBEDGFI`
Roullete Simulator	2025-12-20 09:21	Java roulette simulator. Decompiled with JADX and recovered a custom 16-bit PRNG used for win/loss. Brute-forced the PRNG seed from observed outcomes to predict future rounds, then used a betting strategy to grow balance until a 32-bit signed integer overflow flips it negative, satisfying the “win” condition.
Easiest	2025-12-19 06:01	Windows x86-64 crackme. Traced string references (e.g., `"Enter PIN:"`) in x64dbg back into `main`, identified the numeric PIN check, and patched/bypassed the failure path to reach the success branch and recover the correct input - 8569.
Easy crackme	2025-12-17 17:01	Java `.jar` crackme. Using JADX, I recovered `checkValidity()` which scores the 10-character key by counting how many characters satisfy `(ch & 3) == 0` (i.e., ASCII divisible by 4). A key is valid if the score is exactly 4. I also wrote a small Python keygen to generate valid keys.
crack the points	2025-12-17 11:54	Patch/trainer-style challenge: the program prints "Your count points is %d" with a hard-coded zeroed value. I located the call site in x64dbg/Ghidra and wrote a Python trainer that launches the process suspended, computes moduleBase + RVA, and patches the code to load a user-chosen value into EDX before the printf call. To make the patch robust, I used a trampoline and an allocated code cave (VirtualAllocEx) instead of guessing free space in .text.
puzzle	2025-12-12 01:48	Command-line crackme that hides both its console strings and password check behind a simple XOR-0x9F encoding layer. Using CFF Explorer and Detect It Easy (DIE) for static recon plus x64dbg breakpoints on WriteFile/ReadFile, I traced the input path to a 9-character length check and a character-by-character comparison against an XOR-decoded constant. By NOP-ing the failure branch and single-stepping the comparison loop, I recovered the cleartext password MYPASS123 and confirmed the same XOR-0x9F scheme is used to decode the “Hello World!”, “Enter password:” and “Access Granted/Denied!” strings at runtime.
KeyGenMeV3	2025-12-08 02:14	My first keygen; Win32 GUI crackme with Name + Key validation. Used CFF Explorer for static analysis and x64dbg for dynamic analysis to trace the key validation algorithm. The program processes the name input through a semi-complex encoding function that uses different mixing operations for even/odd characters, involving ROL operations, XOR, and addition with constants. Reversed the algorithm and implemented a Python keygen that generates valid keys for any given name.
decode me	2025-12-01 16:43	Used x64dbg to analyze the main function, bypass a simple IsDebuggerPresent anti-debug check, and follow the calls that read, encode, and compare the user input. The program converts each character to a \xHH form using the format string "\\x%02X" and compares against a stored constant, revealing the correct password.
Ez Crackme	2025-11-30 22:50	Simple .NET console crackme. I used dnSpy to inspect Main, where the program compares Console.ReadLine() directly against a hard-coded string. The correct password is stored in plaintext, so no encoding or transformation was involved.
simple crackme	2025-11-30 09:02	A few months ago I decided to delve into the land of RE. This weekend I decided to put my big boi pants on, take what I've learned thus far, and endure the challenge of my first CTF. Any constructive criticism on the writeup/solution, different approaches, and/or what I could have done better/differently would be greatly appreciated as I am still a scrub and have plenty to learn. :)

2025-12-25 20:55

Windows x86-64 C/C++ console crackme. Traced the password-handling path through std::string helpers in x64dbg and found that the apparent stack constant (`a#l67’gdb`) is a decoy; the real key is computed deeper in the transformation flow. Final password: `4v9cbr217`.

StaticAuth

2025-12-24 22:17

Windows x86-64 “authentication code” crackme solved via static analysis (Binary Ninja HLIL). Recovered the runtime-reconstructed password from lightly obfuscated embedded data; correct code is `goodjob123`.

Assembler Crackme

2025-12-21 02:27

x86 assembler crackme. Traced the password path from `ReadConsoleA` into the validation routine and identified an 8-byte memcmp-style loop against a static byte table. The correct password is the exact 8-byte sequence `@CBEDGFI`

Roullete Simulator

2025-12-20 09:21

Java roulette simulator. Decompiled with JADX and recovered a custom 16-bit PRNG used for win/loss. Brute-forced the PRNG seed from observed outcomes to predict future rounds, then used a betting strategy to grow balance until a 32-bit signed integer overflow flips it negative, satisfying the “win” condition.

Easiest

2025-12-19 06:01

Windows x86-64 crackme. Traced string references (e.g., `"Enter PIN:"`) in x64dbg back into `main`, identified the numeric PIN check, and patched/bypassed the failure path to reach the success branch and recover the correct input - 8569.

Easy crackme

2025-12-17 17:01

Java `.jar` crackme. Using JADX, I recovered `checkValidity()` which scores the 10-character key by counting how many characters satisfy `(ch & 3) == 0` (i.e., ASCII divisible by 4). A key is valid if the score is exactly 4. I also wrote a small Python keygen to generate valid keys.

crack the points

2025-12-17 11:54

Patch/trainer-style challenge: the program prints "Your count points is %d" with a hard-coded zeroed value. I located the call site in x64dbg/Ghidra and wrote a Python trainer that launches the process suspended, computes moduleBase + RVA, and patches the code to load a user-chosen value into EDX before the printf call. To make the patch robust, I used a trampoline and an allocated code cave (VirtualAllocEx) instead of guessing free space in .text.

puzzle

2025-12-12 01:48

Command-line crackme that hides both its console strings and password check behind a simple XOR-0x9F encoding layer. Using CFF Explorer and Detect It Easy (DIE) for static recon plus x64dbg breakpoints on WriteFile/ReadFile, I traced the input path to a 9-character length check and a character-by-character comparison against an XOR-decoded constant. By NOP-ing the failure branch and single-stepping the comparison loop, I recovered the cleartext password MYPASS123 and confirmed the same XOR-0x9F scheme is used to decode the “Hello World!”, “Enter password:” and “Access Granted/Denied!” strings at runtime.

KeyGenMeV3

2025-12-08 02:14

My first keygen; Win32 GUI crackme with Name + Key validation. Used CFF Explorer for static analysis and x64dbg for dynamic analysis to trace the key validation algorithm. The program processes the name input through a semi-complex encoding function that uses different mixing operations for even/odd characters, involving ROL operations, XOR, and addition with constants. Reversed the algorithm and implemented a Python keygen that generates valid keys for any given name.

decode me

2025-12-01 16:43

Used x64dbg to analyze the main function, bypass a simple IsDebuggerPresent anti-debug check, and follow the calls that read, encode, and compare the user input. The program converts each character to a \xHH form using the format string "\\x%02X" and compares against a stored constant, revealing the correct password.

Ez Crackme

2025-11-30 22:50

Simple .NET console crackme. I used dnSpy to inspect Main, where the program compares Console.ReadLine() directly against a hard-coded string. The correct password is stored in plaintext, so no encoding or transformation was involved.

simple crackme

2025-11-30 09:02

A few months ago I decided to delve into the land of RE. This weekend I decided to put my big boi pants on, take what I've learned thus far, and endure the challenge of my first CTF. Any constructive criticism on the writeup/solution, different approaches, and/or what I could have done better/differently would be greatly appreciated as I am still a scrub and have plenty to learn. :)

crackmes.one

crackmes.one

SenorGPT's profile

0

12

0

Crackmes

Writeups

Comments