| Froggate III: Requiem for the Old Order |
@arshi 2 AI filters rang the bell xD
|
2026-10-31 19:25 |
| ChronosKeygenme (brainfuck) |
@arshi I just accept this crackme and you already solve it? I will pay more attention to your solution. It will pass by AI filters patterns, grammars patterns, and I will audit personally your source.
|
2026-10-20 07:38 |
| Simple Frog |
@arshi write a keygen!! It's a experimental crackme to see how you guys will solve it. So I make it simple.
|
2026-09-24 20:17 |
| FROGMAN! |
@anatolianrev Send your write up so I can accept it! Congratulations. Noe face Froggate, the real beast.
|
2026-08-27 21:06 |
| QR Scanner |
After 6 years it was pwned xD. Solution already sent.
|
2026-08-17 20:23 |
| Froginception |
@zuzaaa Waiting your write up :).
|
2026-08-11 23:59 |
| Froginception |
@plainskill what are you doing in a place of reverse engineering if you can't do it?
|
2026-08-11 23:58 |
| Froginception |
[Click to reveal]@plainskill what are you doing in a place if reverse engineering if you can't do it?
|
2026-08-11 23:58 |
| New approach keygen |
You'd posted a keycheck whose image doesn't contain the checksum it's comparing to.
|
2026-08-08 21:20 |
| New approach keygen |
mate, this crackme has no solution because it's BROKEN. So I will patch the part to work properly... You didn't say that can't patch. Nice VM =). If it wasn't broke would be a solid 6.0 quality.
|
2026-08-08 21:08 |
| Boring |
Wow, that was very hard. But I keygened it after all, just waiting my approval solution.
|
2026-07-24 00:04 |
| ComputeTheKey |
Boring zzzzzzz
|
2026-07-16 20:48 |
| Froginception |
@shenmo Nice, write a keygen and a tutorial =)
|
2026-07-05 11:49 |
| MATH keygen |
That's very hard, I don't even think it's keygenable....
|
2026-07-05 05:01 |
| License Checker |
sent =)
|
2026-07-04 01:21 |
| FROGMAN! |
[Click to reveal]It's easy when you use AI to decode...
|
2026-07-02 04:53 |
| Spaghetti Keygen |
[Click to reveal]printf 'PPPPPPPP\n' | ./test_test
Level-up :3
|
2026-06-22 11:53 |
| AI - Almost Impossible |
@Ap0dexMe0 Your writeup is solid from a reverse engineering perspective, but the solver interface is conceptually inconsistent with the actual challenge design.
The binary generates a fresh target on every execution, and the only input available to the user is what is displayed in the GUI. A correct solver should therefore operate solely from that target representation.
However, your solver requires two separate inputs:
compressed_point_hex and encrypted_flag_hex
This assumes prior access to internal components that are not directly exposed to the user in a structured way. In practice, the solver should accept the full target as presented by the application and reconstruct the necessary components internally before proceeding with the attack.
In its current form, the script works more as a validation tool for the analysis than as a proper end-to-end solver for the challenge.
In short:
the reversing is correct, the attack is correct, but the solver interface does not match the real-world usage of the binary.
A complete solution would parse the displayed target automatically and recover everything from a single input, as the challenge intends.
|
2026-04-19 22:47 |
| Lugosi's CrackMe II |
Sorry, there is a bug on this crackme. I will post the corrected version soon. Just cancel this one.
|
2026-02-13 00:33 |