Most public spoofers will leave traces on your machine and get you banned eventually lol.. just use a real undetected cheat and you'll be fine.
This statement is completely incorrect. Here's a technical question for you. When a cheat loads a driver and a spoofer loads a driver do you really think that they're doing it in completely different ways? No they don't. Which means if a spoofer leaves some trace in your services, then so will the cheat do unless its properly taken care of. It'll be the exact same thing. Most spoofers for EAC isnt permanent either so technically there should be no trace unless the developer is retarded, but that also goes both ways.
This statement is completely incorrect. Here's a technical question for you. When a cheat loads a driver and a spoofer loads a driver do you really think that they're doing it in completely different ways? No they don't. Which means if a spoofer leaves some trace in your services, then so will the cheat do unless its properly taken care of. It'll be the exact same thing. Most spoofers for EAC isnt permanent either so technically there should be no trace unless the developer is retarded, but that also goes both ways.
What if the cheat is not using a driver to bypass the anti-cheat?
What a ridiculous answer. I was hoping for a rather intelligent one supporting your claims but nope. In the future I suggest that you read up on stuff before you spread misinformation. You're not even a dev. In one way our another you will need kernel access whether it's through a vulnerable driver, efi bootkit, certified driver or abusing handles. Hypervisor brings lots of fun detection vectors to the mix as well.
What a ridiculous answer. I was hoping for a rather intelligent one supporting your claims but nope. In the future I suggest that you read up on stuff before you spread misinformation. You're not even a dev. In one way our another you will need kernel access whether it's through a vulnerable driver, efi bootkit, certified driver or abusing handles. Hypervisor brings lots of fun detection vectors to the mix as well.
What about a windows API that bypasses any kind of handle stripping?
That requires 0 drivers but just a working windows?
What a ridiculous answer. I was hoping for a rather intelligent one supporting your claims but nope. In the future I suggest that you read up on stuff before you spread misinformation. You're not even a dev. In one way our another you will need kernel access whether it's through a vulnerable driver, efi bootkit, certified driver or abusing handles. Hypervisor brings lots of fun detection vectors to the mix as well.
Well said mate.
Probably another reseller with 0 knowledge talking bullshit.
What about a windows API that bypasses any kind of handle stripping?
That requires 0 drivers but just a working windows?
Please elaborate some more, this is weak and makes absolutely no sense unless you actually explain what you're talking about. Judging by that reply alone it is clear to me that you're no dev and you have no idea what you're talking about.
If you are abusing handles, you are still accessing kernel in one way or another and you'll leave just as many traces as someone who loads a driver and properly clean up after themselves. Abusing handles has their own ways of getting detected as well in addition to your injected data.
