


Also, with the mods installed, I always noticed a flashing window right before the game finished loading which was gone after removing the mods. The first thing I noticed is that GTA V started up fullscreen when I did this, when it started windowed with the mods installed. Again I removed the Fade.exe and all the other stuff, and I then removed all mods but ScriptHook V and its Native Trainer and relaunched the game. Fade.exe had returned after the game had loaded up (not to the menu screen, to the game itself), along with everything else. I then ran GTA V with the mods installed. I first deleted all instances of the Fade.exe folder, the files in the temp folder, and the registry hijack.

Well sure enough, I noticed all the mods that I had downloaded for GTA V had matched the date when this folder was created. I don't go around downloading random programs from non-trusted sources, so I couldn't believe that I had gotten a virus from a program. Now where does GTA V modding come into this? Well, I compared the date of when the Fade.exe instance was created to whatever I had in my download folder. Within that folder was another called Logs, and then two folders with recent dates, and within those were files called Session1.bin, Session2.bin, and so on. I went to the location of this, and found the. exe located in my Temp folder called Fade.exe. Second, not only was the normal system file of the. That was the first red flag, as why would a compiler be accessing the internet? (Again ignorant on this subject, maybe compilers do connect to the internet for specific reasons that I do no know of). First thing I noticed is that it was sending and receiving some data across the internet. This is a normal system file, but I decided to pop open Process Explorer and took a look at the process in detail.

I have never noticed noticed this running in the background, and there really is no reason for a C# compiler to be running in the background because I've never even programmed in C#. I happened to notice that the Windows C# compiler running the background as csc.exe. I tend to do this a lot out of paranoia, just checking that I don't have stuff running in the background that I don't want running, or if I ever possibly run into something that is out of the ordinary that could possibly be malware. I came across something pretty startling today after reviewing my processes that were running on my computer.
