Small HackShield Signatures ByPass :)

[MRx86™]

Originally Posted by supercannon1337

@Raz9r you are saying theory, i am tryng to show you whats going on in output at createthread @ lpthread_start_routine and without calling convention.
What you are sayng there, should be something you have read/studied THEORICALLY, but in facts, as you can see when compiling THIS code(createthread @ lpthread_start_routine and create thread without calling convention), the output will be the same. So if there WAS A MEMORY LEAK with the calling convention, there is even without(or maybe there isnt any memory leak??).
My codes given are providing SAME results(all same opcodes), no difference of stack like you are sayng.

but i guess for you, still, LPTHREAD_START_ROUTINE causes a memory leak.. ok man keep it up, just wanted to notice others that 3/3 of the points you listed in 1st reply are bullshits.


I am referencing @ visual studio 2013 btw

look people like Peter File (Today), R3d_L1n3 (Today), ToxicData (Yesterday), UndercoverUser (Yesterday)
push thanks on his reply, how they being ridiculous by following a retarded!


you still reply to this ****** ? is **** shoot do you understand it ?
is a dumbass i explain same thing to him but dat **** shoot seems complety retarded!

just wanted to try to start drama!
This topic was linked to Learn_more - DC(Drunken Cheetaah) - Pyro666

Oh Yea raz9r Oh Yeah Yeah People laugh about your ******* bullshit raz9r!

[sirosix]

You need to use the visual resolver in case of nullptr, so the caller wont be harmed and there will be no executing loc effektiv, in case of fire break glass.
learn code please boy me pro

[xRoute66x]

#closed