Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I ran into something that kind of worried me today. Lately my computer has been kind of slow and I'm dealing with that, but today when I opened Facebook in Google Chrome, I noticed a message in the bottom left corner while it was loading the site that said "Waiting for localhost". It was brief and I managed to notice it because my computer is slower than it used to & it caused Chrome to hang briefly, long enough for me to read it.

As I'm quite confident in that Facebook isn't running on my localhost, I'm wondering what could potentially make Chrome wait for localhost while I'm loading webpages from external servers. Is there a malware of some kind that I should be worrying about?

Unfortunately I have no other information than this to go on, and I have no idea how to further investigate this, if it generated any logs or whatever.

I'd appreciate any help in figuring out this matter!

share|improve this question

migrated from Aug 19 '14 at 15:56

This question came from our site for power users of web applications.

Have you tried running something like Malwarebytes Anti-Malware? – pnuts Aug 19 '14 at 11:17
Probably a victim of phishing. – Shahar Aug 19 '14 at 14:38
Are you accessing Facebook through secure connection? (https:// in the address bar, padlock icon that says everything's fine when clicked) – gronostaj Aug 19 '14 at 16:02
I'll be sure to give Malwarebytes' Anti-Malware a go & keep you posted on the progress, pnuts! And indeed I'm accessing Facebook through https://, and it does say that everything is fine. That is why it confounds me that the browser insists on waiting for "localhost" for some reason. – Tenaar Aug 19 '14 at 19:24
Check "C:\Windows\System32\drivers\etc\hosts" file. If you see a line like there's your problem. – Jimadine Sep 7 '14 at 8:58

While I do recommend you remain suspicious until you have a satisfactory answer, I have seen some "legitimate" locally-installed webproxy/firewall/filter types of software that do connect to localhost on an alternate port to provide the service.

Also fire this off in a command window as soon as you see suspicious activity:

netstat -b

It might help give some clarity on what is going on.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .