Issue with browser hijacking of Google search results in IE

Squidward

Junior Member
May 26, 2006
21
0
0
Trying to fix an IE issue where google search results are hijacked and displaying pages that are not the ones that should have displayed.

I've already used hijack this!, a coolwebsearch remover software and ad-aware, so far none of them has fixed this particular issue. Host file is clean, TCP/IP settings are fine. There are no objects listed in IE save for Java and Quicktime. So I'm at a loss on what else to look for to remove this.

This apparently is the new adware 'thing' floating around by visiting affected sites. Any help on what else I could try would be greatly appreciated.

Oh and for the record it's Firefox or bust from now on kids. I've had it with this IE ******.
If only FF loaded up quicker, that's the only thing I dislike about it.

 

Squidward

Junior Member
May 26, 2006
21
0
0
The system has Norton AV on it, but it's not detecting anything. Then again, it usually doesn't :) I'll give Antivir a try. I'll let you know if it works.

and it found nothing...

I'm going to have to do some research on this.
 

Squidward

Junior Member
May 26, 2006
21
0
0
No, I haven't posted the log file yet, I really don't see anything suspicious from it either. But I may have to have someone else look at it who has more insight into these types of issues than I do.
 

Squidward

Junior Member
May 26, 2006
21
0
0
I've read about this exploit from other forums, basically the first 3 searches get redirected then all others go the page that was intended, until you start a new browser session. There appears to be variants of the same issue, and any that I've read of that fixed others with the same problem haven't worked for me yet. It's not the 302 site hijack that you linked to, that's a different issue that's a headache for webmasters. It's no doubt some .js code or data object that's the problem, I just can't locate it :(
 

Squidward

Junior Member
May 26, 2006
21
0
0
Thanks for the input everybody, believe it or not, it was fixed by the latest Microsoft update that came out today. Now who would've thought that??? :)