Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ

On Startup FF makes TCP connections to inappropriate website

  • 2 件の返信
  • 0 人がこの問題に困っています
  • 26 回表示
  • 最後の返信者: firefox3080

more options

I was tracing some network activity for an unrelated issue and noticed that when FF starts up it immediately makes multiple TCP connections to livejasmin.com. I have this site blocked by the Windows Firewall and have the host file direct it to 127.0.0.1 so nothing is actually going in or out, but why is FF doing this and how can I fix whatever was done to enable this happening?

I have cleared all cookies and cache, and disabled all addons, and even started in safe mode, but regardless of what I do the very 1st connections that FF makes are always to livejasmin.com, which is obviously not a legit place for FF to be doing any of its routine updates or optimization tasks. My home page is https://google.com and the livejasmin.com connections appear before the 1st attempt to connect to google so this is clearly something malicious that found a way to get into FF early in the startup process.

I have also run 2 different scans tools on the entire computer and both found nothing. I have reviewed all the running processes and do not see anything suspicious either. I do not see this issue with Chrome or Edge, just FF which is my primary browser. All browsers are updated to the latest version as well as the WIN10 OS.

I have also removed my profile and started FF up without the profile, and I noticed the livejasmin.com connections again while the FF "your profile cannot be found" error message popped up. When I had FF make a new profile and set it as the default the same connections to livejasmin.com were made when I restarted FF with the new profile. So it is not tied to my profile.

I was tracing some network activity for an unrelated issue and noticed that when FF starts up it immediately makes multiple TCP connections to livejasmin.com. I have this site blocked by the Windows Firewall and have the host file direct it to 127.0.0.1 so nothing is actually going in or out, but why is FF doing this and how can I fix whatever was done to enable this happening? I have cleared all cookies and cache, and disabled all addons, and even started in safe mode, but regardless of what I do the very 1st connections that FF makes are always to livejasmin.com, which is obviously not a legit place for FF to be doing any of its routine updates or optimization tasks. My home page is https://google.com and the livejasmin.com connections appear before the 1st attempt to connect to google so this is clearly something malicious that found a way to get into FF early in the startup process. I have also run 2 different scans tools on the entire computer and both found nothing. I have reviewed all the running processes and do not see anything suspicious either. I do not see this issue with Chrome or Edge, just FF which is my primary browser. All browsers are updated to the latest version as well as the WIN10 OS. I have also removed my profile and started FF up without the profile, and I noticed the livejasmin.com connections again while the FF "your profile cannot be found" error message popped up. When I had FF make a new profile and set it as the default the same connections to livejasmin.com were made when I restarted FF with the new profile. So it is not tied to my profile.
添付されたスクリーンショット

この投稿は firefox3080 により に変更されました

選ばれた解決策

I have a theory that Process Monitor is looking up 127.0.0.1 in a way that returns livejasmin.com instead of localhost. To test the theory, try turning off name resolution. Example screenshot attached.

この回答をすべて読む 👍 1

すべての返信 (2)

more options

選ばれた解決策

I have a theory that Process Monitor is looking up 127.0.0.1 in a way that returns livejasmin.com instead of localhost. To test the theory, try turning off name resolution. Example screenshot attached.

役に立ちましたか?

more options

Bingo! Thanks jscher2000

livejasmin.com was the first entry in my host file redirecting to 127.0.0.1. I tested by swapping its position and after restarting Process Monitor it showed the name of the URL that is now the first redirect to 127.0.0.1 in the host file.

役に立ちましたか?

質問する

投稿に返信するには あなたのアカウントにログイン する必要があります。まだアカウントをお持ちでなければ、新しい質問を開始 してください。