Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Search Flagging Everything As Potentially Harmful

Posted by Soulskill on from the minor-problem dept.

dowlingw writes "It looks like for the moment at least, all Google results are failing the malware checks and being listed with a warning 'This site may harm your computer,' including all pages from Google themselves. Users trying to visit pages at search results will only be able to proceed via manual manipulation of the search result link to remove the Google click-through (which is also broken). Until Google fixes this bug, it looks Google web search is useless." Update: 01/31 at 15:16 GMT by SS: The problem now appears to be fixed.
Update: 01/31 at 22:01 GMT by KD : Google has now posted an explanation, apologizing and taking responsibility for the "human error" that led to the problem.

2 of 407 comments (clear)

  1. Easier workaround for Firefox users by Ambiguous+Puzuma · · Score: 5, Informative

    Redirect Remover

  2. Explanation from official Google Blog by FleaPlus · · Score: 5, Informative

    Here's the explanation from Google's official blog:

    http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html

    What happened? Very simply, human error. Google flags search results with the message "This site may harm your computer" if the site is known to install malicious software in the background or otherwise surreptitiously. We do this to protect our users against visiting sites that could harm their computers. We work with a non-profit called StopBadware.org to get our list of URLs. StopBadware carefully researches each consumer complaint to decide fairly whether that URL belongs on the list. Since each case needs to be individually researched, this list is maintained by humans, not algorithms.

    We periodically receive updates to that list and received one such update to release on the site this morning. Unfortunately (and here's the human error), the URL of '/' was mistakenly checked in as a value to the file and '/' expands to all URLs. Fortunately, our on-call site reliability team found the problem quickly and reverted the file. Since we push these updates in a staggered and rolling fashion, the errors began appearing between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m., so the duration of the problem for any particular user was approximately 40 minutes.