Speeding up the time a hack/injector gets detected?

[[KGB]Gamingforce]

Is it possible that people are using their injectors/.dll the wrong way and it causes the hack to become quicker to detect?
this is just a prediction from what i am seeing hacks get detected in days when back in 2008 hacks would last for weeks/months.
Just a question from a noob, dont rage or something.

[Josh]

Well the hacks and injectors only become detected after XTrap logs it, plus Z8Games added more content to block/not allow from their database. This means that hacks and injectors are detected quicker, while in 2008, Z8Games wasn't as careful about hacks or foreign programs invading their application.

[[KGB]Gamingforce]

Well the hacks and injectors only become detected after XTrap logs it, plus Z8Games added more content to block/not allow from their database. This means that hacks and injectors are detected quicker, while in 2008, Z8Games wasn't as careful about hacks or foreign programs invading their application.

you clearly weren't around 2008. subagames used run crossfire lol.

[Josh]

I thought that was 2006?

[iSmexy]

its cause of the update in z8games

[CrosLife]

I thought that was 2006?

crossfire did get crated in 2008...

[Josh]

Oh that's odd.. I'm probably thinking of another game

[rkN]

Some users need to educate theirselfs about the difference between patched and detected hacks. You can make hacks undetectable by compiling the code on runtime and injecting it in the memory (kind of bypasses the need for an injector) or just dropping the file and running it. Just add some random strings to the code and compile it with codedom everytime. This will result in the byte hash being different every build thus xtrap cannot find the hash in their database of hashes..