Cheat Engine

zeroc0de · Cheater Reputation: 0 Joined: 31 Aug 2008 Posts: 32

I changed alot of the code, since the debug evasion method failed on the v2.0.

Objectives :

1) Patch the crackme in anyway that will lead you to the good boy message.
2) Figure the password (if you are able to)

You can post the password I don't care. Instead of uploading the patched version of the crackme, just post the patch code, thanks.

Enjoy =P

No VB Decompiler, thanks!

1st one to have figured the password : Sunbeam. Congratulations

pkedpker · Posted: Wed Sep 03, 2008 7:50 pm Post subject:

well as far as I got was..

it uses GetWindowText or something and checks if the application contains

Phantom
Ollydbg
[cpu]
m0dule
module
thr3ad
thread
softiced

in a Instr() function

so thats why you can't attach ollydbg to application it keeps closing or debug in ollydbg..

but after I changed all the names to test1,test2,test3

i managed to get a good runnable program..

But idk how to crack it.. no messagebox or anything.. I found strings with Wrong password, correct password but I can't breakpoint em... so cant do much..

I got close to the password pp0000000 something.. dunno why.. but it was wrong.

eh whatever VB6 programs are harder to look at then C++

zeroc0de · Cheater Reputation: 0 Joined: 31 Aug 2008 Posts: 32

Hehe, there is an easier method of bypassing the debug check : just breakpoint on vbaEnd and then nop the call.

You're not even close to the pass, so good luck finding the rest.

For the messageboxes : I love fake codes. =P

DoomsDay · Posted: Thu Sep 04, 2008 1:40 am Post subject:

In that case, YAY *hint*

zeroc0de · Cheater Reputation: 0 Joined: 31 Aug 2008 Posts: 32

DoomsDay · Posted: Thu Sep 04, 2008 10:18 am Post subject:

I know xD
just pointed it out =]

G0DFATHER · Posted: Thu Sep 11, 2008 9:14 am Post subject:

Damn it is hard