CA Updates

Hey guys,

Some of you might remember me from a year ago in the CAEU section.
I didn't follow CA for quite a while and now i'm wondering whats new?
Any major new hackshield/security updates?

Hope some coders can help me get up2date again

Memory edit is completely detected, ptc doesnt work for all commands.
Cant remember more atm, just happy with charhack and unl ammo, I dont need more^^
I just wanted to prove that I can simply make unl ammo for ca no matter what they'll do :P

You are working on CAEU am i right?

Originally Posted by Ch40zz-C0d3r

Memory edit is completely detected, ptc doesnt work for all commands.
Cant remember more atm, just happy with charhack and unl ammo, I dont need more^^
I just wanted to prove that I can simply make unl ammo for ca no matter what they'll do :P

So what is the best way to memory edit now? Are the addresses just scanned on respawn like old times or did they actually upgrade past that?

Originally Posted by |-|3|_][({}PT3R12

So what is the best way to memory edit now? Are the addresses just scanned on respawn like old times or did they actually upgrade past that?

You cant memory edit at all with bytechanging (Just with VEH/SEH and breakpoints [HWBP are UD on NA])

Originally Posted by Ch40zz-C0d3r

Ey, ich kann ja nix dafür dass nexon einfach nur schlecht ist xD
Die werden mich niemals los^^ (Hatte btw auch > 1 Jahr Pause weils lw war, hat sich leider nix geändert. Ist sogar noch leichter geworden xD)

Yes, but NA is nearly the same.

Well then, i can remember when i stopped coding, i stumbled on a problem which was that Nexon is now scanning for Injected DLLs and then crash the client. How did u fix/bypass this?

Originally Posted by steven1578

Well then, i can remember when i stopped coding, i stumbled on a problem which was that Nexon is now scanning for Injected DLLs and then crash the client. How did u fix/bypass this?

Well they cant just kick you for an injected dll (which they get through FS[13] Register => PEB) so they made signatures of your hack.
YOu have to encrypt it very well so their signature will fail. Had problems with it too :P

Originally Posted by Ch40zz-C0d3r

Well they cant just kick you for an injected dll (which they get through FS[13] Register => PEB) so they made signatures of your hack.
YOu have to encrypt it very well so their signature will fail. Had problems with it too :P

So instead of using the "XorStr" i used before i need to use a new encryption method, is that what u mean? Will packing my DLL fix this too?

Originally Posted by steven1578

So instead of using the "XorStr" i used before i need to use a new encryption method, is that what u mean? Will packing my DLL fix this too?

Well the encryption should be ok, you have to change public code because they are scanning for it. Use some strong packer + virtualizer and youre done

EDIT: In my last post I meant wirh encryption the encryption of bytes in your hack, not your strings :P

CA Updates

Post a Reply

Similar Threads

Tags for this Thread