Let me perhaps explain this a little bit. Forgive me if I had been a bit rash, maybe I should explain this a bit more fairly. Software such as Discord utilizes code injection in order to power their overlay. This utilizes the following Windows APIs: https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-virtualallocex https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-writeprocessmemory https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-virtualprotect https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createremotethread Extreme Injector simply utilizes their APIs in the same manner Discord does in order to inject "code." While extreme injector itself can be used for cheating, its overall purpose is simply "code injection," which is commonly seen in many programs with completely non-malicious intentions. There is FAR better ways and non-intrusive means to check if a player is truly touching Destiny that is employed in 99% of games. Take a case example: VAC games check their process PEB (https://en.wikipedia.org/wiki/Process_Environment_Block) to scan the modules list and determine is a foreign module has been injected into their game. This is still not enough reason to prove someone is "hacking" as a lot of software injects modules into runtime processes for a multitude of reasons. VAC signature scans these modules and compares them with an online db to see if any of the bytes sigg'd are similar to cheats, and then they push a ban. Games that have a lot of hours poured into them shouldn't have such poor checks, and there is a million and one ways to actually determine if someone is truly messing with Destiny other than just scanning through the process list. You shouldn't be banned for using a "code injector" on something not related to Destiny, and they can completely check if you are using it on Destiny. I know because I literally programmed anti-cheats. They can hook their own loaded WinAPI functions and see if you are injecting any DLLs (LoadLibraryA/W can easily be hooked). They don't need to do this, and it is completely ridiculous. It is needless and you can also easily bypass this check by coding your own injector (which is about 5 lines of code).