.Lawliet (05-26-2014)
So lets say I just released a hack/macro. And after a few days it gets detected, but not patched. How is XingCode detecting it? Via memory? Or when something is hooked/attached into the game?
Also since it's only detected, if I re-compile my application would it still work?
I'm thinking to create a macro which has the functions like Builder and Stub. So the member can create the macro, (of course not literally create, re-create the application with existing codes in the stub), since the executable is re-created would that make it undetected again?
Thanks.
.Lawliet (05-26-2014)
****** Open Handles can lead to a scan, random scans, strings, writing to read only pages, IAT, Peb(linked modules), Splicing hooks also known as detours, and signatures
Static: Fileinfos in combination with size, strings(pdb path for ex), IAT.
Catch-on Scans: Xigncode stores some detections in temp under a random file with dll extension, mui cache.
jaydeeph (05-25-2014)
Thanks bro .
@Riddick requesting a close on this thread, thanks bro.