Rundll32.exe causing blank javascript windows to pop up periodically

Toy_Reid

Reputable
Oct 19, 2014
17
0
4,510
Yesterday I was playing a video game and noticed my computer slowing down immensely. I looked in my processes to see dllhost.exe was consuming almost the entirety of my CPU and physical memory. I searched and searched and finally found a solution in this post: http://malwaretips.com/threads/dllhost-exe-32-com-surrogate-hijacks-my-computer-help.33289/.

After using the Farbar Recovery Scan Tool, I started noticing blank white windows popping up with some sort of javascript address at the top (pictured here: http://i.imgur.com/hqZ8UwY.jpg). These windows pop up every ~3 minutes and never have any content, although the address at the top is different, as far as I can tell, every time.

I downloaded Malware Bytes and did a scan, it did not fix the problem. I used the Windows Malware Recovery Tool, which at first did fix the problem, however after restarting my computer twice, it started occurring again. I also did an SFC Scan, which found no errors and didn't fix it.

I have associated this problem with the rundll32.exe application. Whenever I close the javascript window, the rundll32.exe program closes under the Processes in the task manager. The reciprocal happens as well, when I end the rundll32.exe process, the javascript window closes. I am concerned that my rundll32 may be infected, as the icon in /System32/ looks quite unusual: http://i.imgur.com/5kRlnwf.png.

Any help would be greatly appreciated--the blank window always pops up at the top of the screen and as such makes me forcibly reselect the window I was previously interacting with (which is very annoying when playing games.) Thank you in advance.

Edit: I just booted my computer into safe mode and this problem still occurred.

P.S. - After using FRST I am also having a problem where when navigating folders, any folder I open is opened in a new window. I have the folder option checked to open folders in the same window, so I am unsure what is causing this problem. This issue is obviously not as important as the first one, but still annoying nonetheless.