We don’t really have any ability to say what so ever either way, so at best its just guesswork.
Here’s a few worthwhile notes though:
-
The global injection service in SKIF is not actually a part tied to the Special K Injection Frontend (SKIF) itself. You can start the global injection and then exit SKIF – the global injection will still remain active in the background.
-
This was partially not the case with SKIM, where SKIM64.exe took care of 64-bit injection while a background process rundll32.exe took care of the 32-bit injection.
-
In case of SKIF, I believe both 32-bit and 64-bit injection is taken care of by background rundll32.exe processes that retains the global injection service even if SKIF is closed down without stopping global injection.
-
The reason behind this design was to allow the use of Special K on Steam without the user appearing as “In game: Special K” for their friends on Steam.
-
-
Special K won’t be able to inject itself into any games running with elevated privileges unless the user does unexpected stuff such as running SKIF/SKIM/the global injection as an elevated process.
-
Games running with elevated privileges are typically the case for those using BattlEye, Easy Anti-Cheat, and a few other in-house anti-cheat solutions.
-
Though I have no idea what anti-cheat Modern Warfare makes use of, or whether it runs the game in an elevated process or not.
-
-
Special K’s global injection works through a Windows method that technically sees Windows injecting the DLL files into all applicable running processes (basically all that is running within the same user context). The whitelist/blacklist of Special K then determines whether the DLL functionality should actually “initialize” fully, or if the DLL file should remain entirely idle within the process.
- The initial implementation of this form of global injection also saw Special K eject itself from processes if it found itself in a non-whitelisted process, but since it’s Windows that injects the DLL file, Special K would just be re-injected into the same process immediately after. This created insane issues where SK got injected/ejected out of processes hundreds if not thousands of times per second, and so the method was redesigned to leave the DLL file remain in an idle state instead until the global injection was stopped.
Therefor it is theoretically possible that you started the global injection service of SKIF, then closed down SKIF without stopping the global injection service (so global injection remained active in the background), then the game (or Battle.net) might’ve launched a process that ran within the same security context (the user-space) as the global injection, causing Windows to inject Special K into the process. That alone, even though Special K didn’t initialize properly or actually manipulated anything, might’ve been enough for Modern Warfare’s devs to call foul and throw the banhammer at you despite evidence of cheating.
But as mentioned it’s basically guesswork. The risk is there, yes, but only Modern Warfare devs can confirm whether or not Special K was actually why you were banned.