Ideas Anti Detection

Best Way still is Unpack and pack again!

I've never crashed with mpgh open either. I do however (rarely) crash some times when I alt tab out

People should just download the source of GC and obfuscate all the shit

I was thinking along the lines of what Whit said, As its a common method used to scan processes and get the titles of each windows. Anyway besides that implementing these random names and overlay is actually extremely easy to do for an injector, it just a simple matter of making a copy of the original dll make a random string to name it open it as a stream and place some random bytes at EOF(you could do this during the copy process of the original dll) because its at EOF the code never gets executed an its just a an overlay type of thing, As matter of fact we could use the random string that we used for the name of the dll, and use that to append to the EOF which would give us our random bytes or just add that string as a resource string instead of adding to EOF.

Wow, this is a great idea! I would love to see this in your injector along with the new combo-box i suggested .

Yeap I will adding that today after a few tests have been carried out, for example the injector has an option to close it self after injection, But if we have made a copy of the dll I need the injector to monitor the Engine process so when it closes it will delete the copied dll from HD otherwise we end up with a heap of duplicates with different names, The injector Already Monitors the selected process anyway if it has'nt been set to Auto close... I am thinking to make a temp Directory with a unique name and when the Injector first loads again it can delete this directory(which contains all the copy's of the dlls) thus removing the clutter of multiple dlls. I will think about it later today how to remove copied dlls if Injector is set to close on injection and hopfully come up with a solution that wont clutter the users HD with a heaps of dlls

Departure, I've seen your supposedly undetected new method of injecting, and now you're bringing this up.. Kinda useless imo, probably a bit mean but true. HS doesn't give a shit if you inject. They hook the functions they want no one else to hook and check where its returning, if its returning to an unknown module then they detected something.

Srs, they dont care if you inject, Idk if you've noticed, but you can inject a DLL that does nothing and you will never crash.

This is very true.

@everyone
Unlike other games combat arms would take any injection as long as the .dll is not meant to crash it on purpose.

Like for example, Crossfire detects injections if not hooked/whatever correctly. You inject a hack that has very bad coding or just detected it will crash at start.

lol idk what i am saying! goodbye

Undetected injection has nothing to with changing the hash or CRC32 of loaded mapped image which is the reason I bring this up in the first place as I hear people saying that they changed the filename of the dll and it was magically undetected( Personally don't believe this) but I can maybe believe that they use some hashing procedure to get a sum of any attached images to its processes, Which also has been said from the replys changing a single byte has helped them make there hacks undetected again, Also makes no logical sense to use packer as the code is unpacked into memory which would make this useless, but yet people still do... So its only common sense they must be scanning and hashing memory if what others say is true.

As for the "Undetectable" injection method, This doesn't mean your hack is undetectable, This only means I use a method which has no documentation of its API in use with creating a remote thread, Which means games that hooks "CreateRemoteThread" API wont detect this method as it doesn't use this API. Also what must be noted is the D-Jector is not tied to only combat arms and therefore adding these option can and will be useful for other games.