Jump to content
Tuts 4 You

[keygenme] keygenme 2


Recommended Posts

Posted

Virus scanners detects:


TrojanDropper:Win32/Jevafus.A


Posted

That would be the packer. I used obfuscation in the packer, as well as the keygenme.


Posted (edited)

easy unpack, never seen the packer before, though. What is this?

Edited by deepzero
Posted

That would be my own packer.


 


It does give positive feedback on a proper serial though, is that what you mean?


Posted

MessageBoxA. I think it was meant.


Posted

Yes, a MessageBox is given on valid serial.


Posted

I always have same value:


 


 



CMP DWORD PTR SS:[EBP-0x358],EAX
[EBP-0x358]=00000060  

It's correct?


Posted (edited)

Odd, any exact address?


 


EDIT: tried debugging my code, my keygen works on my system :/


Edited by mudlord
Posted

yeah, that looks like a off-by-4 bug to me, too.

Looks like you are comparing the return address instead of the serial dword.

e.g.

 

 

00402929                         .  3985 9CFCFFFF                 CMP DWORD PTR SS:[EBP-364],EAX

 

stack:

 

0012F554      2A323106 //value that is in eax, too0012F558      E9988CC8 //actual part of serial0012F55C      77F16BF2  RETURN to GDI32.77F16BF2 //some return addresss

state/pane:

 

EAX=2A323106Stack SS:[0012F55C]=77F16BF2 (GDI32.77F16BF2)

 


Or mybe it`s just a nifty trick? ;)


 

Posted

Matches fine in my keygen....;)


Posted

Ah, so it is a trick?


Anyways, it`ll have to wait for tomorrow... :tired:


Posted

For this address 0040267B value always 60. But it is set earlier this address 00403387. Ok?


Posted (edited)

looks like you are running into issues with the obfu/antidebug (used BeaJunker macros ported to C) :< If people prefer, I could leave the packing code as-is and remove the obfu in the checking code? Not sure why it would be interfering though.


Edited by mudlord
Posted

could you drop off an example name/serial combo to verify that it actually owkrs? (only if it doesnt ruin the challenge, ofcourse...)


Posted (edited)

For my hardware


mudlord


N+NGKVDLDk+8pESolBZYNNvZVQHqd6oNQTpQn+Mf2Gs=


 


was intending the crackme to be HWID based, should have added a HWID label in the crackme :<


Edited by mudlord
Posted

Don't know. I unpack and kill obfu/antidebug.


Posted (edited)

Okay, so it was not working properly at all.


Sorry for the issues, should have tested more.


 


Back to the drawing board I suppose. :<


mudlord_keygen.zip

Edited by mudlord

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...