Thanks for your input, im not a good coder, so maybe i will do it better next time :)

Yes, it shouldn't work for other Packed file.

Your Loader need add code loop(for/while) to detect WMProtect have been decrypted your app code(Real code you need patch), verify it then byte is exist, you will be suspend process and patch code before resume process.
That's all

BR,
quygia128

It works as long as you insert the correct offsets. It works on all VMProtect with self-checks as well as Safengine's selfcheck, tested on multiple protected files and i have cracks released with this loader for weeks without complains.

It still depends on the hardware (CPU power) of the machine. I have done a VMP loader myself in the past and I had to use Sleep() with a certain amount of time. The good thing is that you can automatically bruteforce the correct Sleep time more or less for a specific machine.

Real release groups don't allow "loader" cracks for obvious reasons.

For VMProtect and Themida/WinLicense,
Here is my method for loader.

1. Hook the API near OEP or near your patch point.
2. Check the return address from stack.

Then, you know when your target is unpacked.

Are you talking about my loader?
I'm not sure if i understood you correctly, because the source i posted here does not depend on hardware/CPU becuase it does not use sleep.
Sleep is a method i would never use at all, its shit, cuz yes as you said CPU.

I accept your critizism but i released my source to be nice, so that people that may not be "that" expericed with this, might solve it with my working method as well as giving people an idea to work on, and on how it could done.

To be honest i couldnt give two shits about what real release groups allow or not.
In my eyes, a working method is a working method, as long as the program opens, I'm happy and the users that use it will remain happy.

Good day.

0x22:

Easy tiger. I know your good intention of bringing the loader source here (although imho it doesn't help much). But honestly I think you should improve your code, and make it more universal, make it available on more machines.

It works on your computer, well ok. It fits your needs, ok.

The people just state here that they think you need to do more than that. Slapping a little bit on your ego isn't comfortable for you, but do accept it as a challenge. Don't be a kid or you will forever stay at your "level".

You can listen to my advice or not, it depends on you. However, satisifying yourself with little achievement won't take you far.

My two cents.

I am not a good coder, too.
So, if I share my source codes, they will surely be ugly.

But I think we share source codes, methods. And with help from more friends here, we work out new and better solutions together.

I love to learn, i have no issues with learning, i learn every day and i enjoy it.
One of the cracks i used this loader on has 8291 unique logins in my php panel as we speak, and not a single complaint.
So i dont see the reason to rip on something that work.

Yeah, It is very useful especially for patching child process created by father process; such as Armadillo, SDProtect, etc.

I always use hook method when loaders like dUP2 fails to patch on time.

So if the VMProtect does not check for API hooking, this method is the best.

Problem is ,like themida, vmp uses emulated api as well . so normally its hard to predict which api is "universally free" from api emulation and thus hooking doesnt work in all cases

This has worked bulletproof on VMProtect, Themida and Safengine for several dozen of loaders for me, never had any problems with using this method tbh.

As title says "SIMPLE" so thst is what this is.... simple loader. But as I can see after so many suggestions and criticism maybe some of you could show user 0x22 how to "ADVANCE" it...
;)

i dont see any link between your message and my statement . it doesnt apply to your method at all .

I'm sorry i must've misunderstood, my apologies :o