Avast WEBforum
Other => Viruses and worms => Topic started by: REDACTED on November 07, 2015, 03:45:21 PM
-
... by Avast browser plug-in. Why? Is there some secret we don't know?
-
post a screenshot of the avast popup warning
-
Anyone get an answer for this yet? Keeps marking google for phishing site for me too.
-
Let's try this again.
-
Thanks ranald2, I couldn't get mine to post but that is what it looks like.
-
Already 3 people who reported this now in just a few hours. ???
-
No problem here IE11
-
OK, if I start up Firefox, all tabs that ref. www.google.com display Phish warning as shown in attachment. IF from the primary Firefox window I open a second window from firefox for www.google.com, then no phish warning. Also happens with Chrome.
-
You are correct, sir, isn't a problem on IE.
-
This is FF I do not use it a lot
Unfortunately I can only get Google.co.uk as the com domain is barred to me
-
Eddy, are you saying we should have searched before posting?
-
I dont this warning inside Chrome on Windows 10 Threshold 2 64-Bit :)
Over on MalwareTips its also reported.
-
Here it is from Chrome.
-
Must leave for errands. I'll check back later.
-
This is FF I do not use it a lot
Unfortunately I can only get Google.co.uk as the com domain is barred to me
If you use this URL https://www.google.com/ncr (https://www.google.com/ncr) the /ncr = No Country Redirect so it should always go to google.com
EDIT: I have now visited google.com and no warnings.
-
Lucky guy. I'm still blocked.
-
Looking at your image again, this is the AOS kicking in and I haven't installed the avast Browser Protection (AOS) on this system. That could certainly be the reason, but if it is being flagged by the AOS, I would expect this to migrate to the Web Shield detections.
It is somewhat strange, if this were very widespread the avast stats should be ringing alarm bells on a massive site being flagged.
-
I, too, am getting the same message. Also, at the top of my Google screen is a red circle with an exclamation point. When I click on it, I get:
THIS SITE IS NOT SAFE
You rate this site as positive .
0 TRACKING SYSTEMS
on website
google.com
Social networks (0)
Ad Tracking (0)
Web Analytics (0)
Others (0)
GLOBAL SETTINGS
Tracking systems are currently blocked
Allow all tracking systems on all websites
More settings
Online Security
-
When I click on the red avast icon and ask for more info, attached is what I see.
-
Can confirm that this is happening here as well, strangely with http://www.google.com but not https://www.google.com
-
@SenorOcho: Can confirm, im now blocked too for whatever reason.
-
I am getting the same warning message as everyone else has posted. I am using Firefox 42.0 on Win7.
Doesn't appear to be a problem on Chrome.
Anybody have a suggestion? Has anyone just clicked "Trust this domain"?
-
Eddy, are you saying we should have searched before posting?
No, I just said that multiple people see it.
But (re)search(ing) before posting is strongly advised.
Many thing have been explained.
Many questions haven been answered.
For many problems a solution is already provided.
-
I too got this today, attaching screen shot. Here's the difference - I'm running LINUX Mint 16, and do not have Avast installed on this side. I'm dual booting Windows XP and it is installed on that side. I'm thinking maybe I installed the Chrome plugin at some point? Who knows. But I got it as well. Now what do we do?
-
Same problem here using Chrome on Android. Samsung Galaxy S5 to be exact.
-
Ok, it looks like simple a FP to me.
My questions is...
Did any of you people reported it to avast ?
-
This is FF I do not use it a lot
Unfortunately I can only get Google.co.uk as the com domain is barred to me
If you use this URL https://www.google.com/ncr (https://www.google.com/ncr) the /ncr = No Country Redirect so it should always go to google.com
EDIT: I have now visited google.com and no warnings.
It's Firefox version dependent apparently as it's still a problem with my version 40.0.3, see TOPIC HERE (https://forum.avast.com/index.php?topic=178825.msg1265721#msg1265721)
-
It's reported in the support forum also. How to report to Avast? I am using free version, so I don't have the required order confirmation number and billing address required for their contact support form.....
-
Still happening on Chrome for me.
-
Happening on my HP Chromebook 14 and Windows 10 64-Bit in Chrome. Only with the default Google homepage for Chrome, if I manually type google.com it redirects to https://www.google.com/ without a problem.
-
Interesting. Now, if I type "www.google.com", it re-directs to "https://www.google.com/?gws_rd=ssl", and that generates the Avast blocker. IF, on the other hand, if I type "https://www.google.com", Avast approves and displays the page. So, it looks to me like the google re-direct, "https://www.google.com/?gws_rd=ssl" is where Avast thinks the Evil lives...... Same thing in Chrome as in Firefox.
-
Hi ranald2,
What happens when you have disabled https scanning in Avast. Is all coming back to norms then?
polonus
-
This is FF I do not use it a lot
Unfortunately I can only get Google.co.uk as the com domain is barred to me
If you use this URL https://www.google.com/ncr (https://www.google.com/ncr) the /ncr = No Country Redirect so it should always go to google.com
EDIT: I have now visited google.com and no warnings.
Thanks David tried that and still no warnings...
-
Howdy,
Disabling Avast Online Security Browser in Firefox solves the problem. I don't see a way to specifically disable HTTPS: scanning within that.
-
Having same issue in Chrome on Mac OS. https://www.google.com works, https://www.google.com/?gws_rd=ssl redirect flags
-
I am located in the USA, Eastcoast and getting the same warning.
-
We are really sorry for your inconvenience, we are working on fix but we have some technical problems.
One more time sorry for your inconvenience,
Jan sirmer
-
Fix is release
sorry for your inconvenience,
Jan
-
It appears to have cleared up for me at least. Thanks.
-
Yup, it is not flagged on my computer either.
The only affected URL was "https://www.google.com/?gws_rd=ssl", and while the fix is now live, we continue to investigate why this actually happened and what steps we will implement to prevent similar false positives in the future.
Thank you for your reports, which made us realize the false positive as soon as possible, and also thank you for your understanding ;)!
Honza
-
Thank you.