Hello, so i tried many time to bypass memory détection using fake scan page method but i get always a crash. i added an infinite loop before return original page then xcrap call the function without any return, well i dont get a crash only after few minutes. So i was asking if the method is patched or if i'm doing something wrong and if i need to detours another func.
It's a lot better to remove the xtrap driver. You can do that by preventing it from starting up(You have to make it look like xtrap is still there). You can also hook functions. There are several other methods.
It's a lot better to remove the xtrap driver. You can do that by preventing it from starting up(You have to make it look like xtrap is still there). You can also hook functions. There are several other methods.
xtrap driver != memorydetection ;o
Quote:
Originally Posted by Forbidi
Hello, so i tried many time to bypass memory détection using fake scan page method but i get always a crash. i added an infinite loop before return original page then xcrap call the function without any return, well i dont get a crash only after few minutes. So i was asking if the method is patched or if i'm doing something wrong and if i need to detours another func.
thats cause xtrap has a new check for this function. you can bypass it by hooking some functions before it and using maybe a vtable hook ;o
Well comparing 'size' for being smaller than zero is actually much safer than expecting that 'size' would never be smaller than zero. Be prepared for the worst case scenario
I don't think it's a good idea to share everything we know about XTrap with the wide public, you were able to find the memory detection by yourself so you should be able to find other functions as well.
Quote:
Im not using multithreading, i will add the conditions and see thx.
No, you aren't using multithreading, XTrap uses multithreading and you're hooking a XTrap function.
std::mutex might be something for you.
Oh, and you should return TRUE in your DllMain, return FALSE will free the allocated memory thus your hook jumps to some random / empty memory.
Well comparing 'size' for being smaller than zero is actually much safer than expecting that 'size' would never be smaller than zero. Be prepared for the worst case scenario
xtrap is checking if its zero too =P
Quote:
Originally Posted by Forbidi
What func you mean Oo
just backtrace
Quote:
Originally Posted by snow911
No, you aren't using multithreading, XTrap uses multithreading and you're hooking a XTrap function.
std::mutex might be something for you.
if you let xtrap scan in copied pages you dont need a mutex d:
XTrap Bypass[Tutorial] Anti Memory Detection 05/31/2013 - S4 League Hacks, Bots, Cheats & Exploits - 21 Replies Einen wunderschönen guten Abend,
ich verkünde frohe Botschaftich hab herausgefunden wie man den Bypass von iKasaii benutz mit 2 anderen Bypässen Links werde ich zu den einzelnen Bypässen posten.
Hier ist das Tutorial:Anti Memory Detection Hacking
Und hier die Links zu den Bypässen:Xtrap Bypass(Delphi/C++)
Decay' Bypass!
fix memory detection 03/03/2013 - S4 League - 4 Replies Hi there.
I am wondering, how can we fix that 15 mins detection? Is the problem on the bypass or in the trainers?
XTrap Memory Access Detection, Profi Tipps benötigt. 06/12/2010 - S4 League - 3 Replies Gestern habe ich paar Adressen gefunden die in Frage kommen könnten.
Einmal die SP Regneration, Cut Speed und noch paar andere.
Bei jede Adresse in der ich die Value ingame verändere meckert XTrap NICHT. Nur bei den besagten Adressen da kommt ne Meldung "Memory Access detected" .
MrSm!th hat ja einen Bypass für die CheatEngine detection gemacht, kann man das nicht auch für die bestimmten Adressen machen?
Wie muss man da vorgehen, welche Datei von Xtrap muss man analysieren oder muss...
