[FRST.txt Attached] System Null Process High CPU Usage

[ShinobiSamurai]

Hello there!
While trying to download an cracked application via torrent, I somehow managed to infect me PC with an malware/adware/rootkit. I was able to have Zemana and Malware Bytes (free trial version) installed before the real issues begun which was able to block all the link hijacking and auto web page opening attacks but seems like I have a System Null Process running in my background with very high CPU usage, which under further investigation lead me to believe that it is redirected to svchost.exe under the SysWOW64 folder which is situated in C:\Windows.
While Zemana and Malwarebytes both detect the issues Zemana directs the issue to svchost.exe and Malwarebytes shows Malware, after "fixing' the issue and a reboot the same issues re-appear again while performing another scan.

Moreover, While trying to download FRST/RKill/Rouge Kill my browser (Chrome/Firefox/Edge/Opera) automatically closes. Even more anything which I try to download containing the keyword "Anti-Malware", "Anti-Rootkit", "Anti-Virus", gives me the same results.

I am hereby attaching my full scan report of FRST which includes FRST, Addition and Shortcut analysis which has been done in Windows Safe Mode for your kind help!

 

[TwinHeadedEagle]

Hello,

Fix with Farbar Recovery Scan Tool

This fix was created for this user for use on that particular machine.

Running it on another one may cause damage and render the system unstable.

​

Download attached fixlist.txt file and save it to the Desktop:

Both files, FRST and fixlist.txt have to be in the same location or the fix will not work!

• Right-click on
  
  icon and select
  
  Run as Administrator to start the tool.
  (XP users click run after receipt of Windows Security Warning - Open File).
• Press the Fix button just once and wait.
• If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
• When finishes FRST will generate a log on the Desktop, called Fixlog.txt.

Please attach it to your reply.