[ Hidden Content! ]
So this is how to make your loader secure.
First of all you would want to add some Anti-debugging tricks, and you want your code to be secure. How can your code be secure? By having complicated code and not copy pasted code from public resources.
Other ideas would be for you to have as many checks as you can, perhaps on multiple threads. And to change stuff from time to time. I would also encrypt the contents of your DLL file(s) and the text strings. Also, I would pack the loader and after injection you could change something in the DLL file(s), perhaps a bitflag or a jump without whom the cheat wouldn't work?
First of all you would want to have as many seperate memory pages as you can get. I would also add some anti-debugging tricks and you would want for your code to be secure. How can your code be secure? By having complicated code and not copy pasted code from public resources. Other ideas I can come up with is for you to have as many checks as you can example: Hash, Heartbeat, etc, perhaps on multiple threads. I would also encrypt the text strings and I would recommend making your own hooks because public hooks are easy to backtrace. I also wouldn't rely on WINAPI's as they can be hooked and backtraced easily. And if you like intent to send() something, maybe you could do it via the game's wrapper? I would also change stuff from time to time and pack the DLL.
First of all you would want to add some Anti-debugging tricks, and you want your code to be secure. How can your code be secure? By having complicated code and not copy pasted code from public resources.
Other ideas would be for you to have as many checks as you can, perhaps on multiple threads. And to change stuff from time to time. I would also encrypt the contents of your DLL file(s) and the text strings. Also, I would pack the loader and after injection you could change something in the DLL file(s), perhaps a bitflag or a jump without whom the cheat wouldn't work?
First of all you would want to have as many seperate memory pages as you can get. I would also add some anti-debugging tricks and you would want for your code to be secure. How can your code be secure? By having complicated code and not copy pasted code from public resources. Other ideas I can come up with is for you to have as many checks as you can example: Hash, Heartbeat, etc, perhaps on multiple threads. I would also encrypt the text strings and I would recommend making your own hooks because public hooks are easy to backtrace. I also wouldn't rely on WINAPI's as they can be hooked and backtraced easily. And if you like intent to send() something, maybe you could do it via the game's wrapper? I would also change stuff from time to time and pack the DLL.
Also, please notice that you cannot make your Loader and DLL file(s) 100% secure, you would want them to be safe enough that the crackers will just give up.