{"id":2647,"date":"2016-04-25T15:57:53","date_gmt":"2016-04-25T21:57:53","guid":{"rendered":"http:\/\/www.whitefirdesign.com\/blog\/?p=2647"},"modified":"2016-04-25T15:57:53","modified_gmt":"2016-04-25T21:57:53","slug":"google-needs-to-improve-the-review-process-for-websites-labeled-this-site-may-be-hacked","status":"publish","type":"post","link":"https:\/\/www.whitefirdesign.com\/blog\/2016\/04\/25\/google-needs-to-improve-the-review-process-for-websites-labeled-this-site-may-be-hacked\/","title":{"rendered":"Google Needs to Improve the Review Process for Websites Labeled &#8220;This site may be hacked&#8221;"},"content":{"rendered":"<p>Early last year Google changed some of the underlying technology used in their process of of handling\u00a0websites they suspect of being hacked (which leads to a &#8220;This site may be hacked&#8221; message being added to listings for the websites on Google&#8217;s search results). More than a year later\u00a0we are still finding that the review process for getting the&#8221;This site may be hacked&#8221; message removed after cleaning up such a website is in poor shape and likely lead leading to a lot of confusion for people trying to navigate it if they don&#8217;t deal with it&#8217;s problems on regular basis (like we do). While we think that what Google is doing by warning about these situations is a good thing, the\u00a0current state of the review process is not acceptable.<\/p>\n<p>To give you an idea of what are people are dealing with lets take a look at what we just dealt with while getting Google to clear a website we had cleaned up.<\/p>\n<p>Once you have cleaned a website with the &#8220;This site may be hacked&#8221; message, you need to add the website to <a href=\"https:\/\/www.google.com\/webmasters\/tools\/home?hl=en\">Google&#8217;s Search Console<\/a>\u00a0and then you can request a review in the Security Issues section of that.\u00a0That section will also give you information on what Google detected:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2649\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-1.png\" alt=\"security-issues-page-1\" width=\"974\" height=\"415\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-1.png 974w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-1-300x128.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-1-768x327.png 768w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>In this case Google detected that spam pages were being added to the website, which they refer to as an URL injection.<\/p>\n<p>Before requesting a review last Monday, we doubled checked that the spam pages no longer existed using the Fetch as Google tool in the Search Console, which allows you to see that what is served when a page is requested by Google. The URL they listed on the Security Issues page was &#8220;Not found&#8221; when we used the tool, indicating that the spam page was no longer being served to Google.<\/p>\n<p>On Tuesday a message was left in Google&#8217;s Search Console for the non-www version of the website&#8217;s domain indicating that\u00a0hacked content had been detected:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2651\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-non-www.png\" alt=\"seach-console-message-non-www\" width=\"1158\" height=\"275\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-non-www.png 1158w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-non-www-300x71.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-non-www-768x182.png 768w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-non-www-1024x243.png 1024w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>Considering that Google was already listing the website as having a security issue for several days you might think this was a new detection, but it wasn&#8217;t. In the security issues section it still listed the old last detected date:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2652\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-2.png\" alt=\"security-issues-page-2\" width=\"935\" height=\"98\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-2.png 935w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-2-300x31.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-2-768x80.png 768w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>Using the Fetch as Google tool in the\u00a0Search Console we requested the URL again and it was still &#8220;Not found&#8221;:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2653\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-19-2016.png\" alt=\"fetch-as-google-4-19-2016\" width=\"1153\" height=\"41\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-19-2016.png 1153w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-19-2016-300x11.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-19-2016-768x27.png 768w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-19-2016-1024x36.png 1024w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>Then on Wednesday the same message was left for the www version of the domain:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2657\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-www.png\" alt=\"seach-console-message-www\" width=\"1166\" height=\"325\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-www.png 1166w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-www-300x84.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-www-768x214.png 768w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/seach-console-message-www-1024x285.png 1024w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>Again the last detected date in the Security Issues section hadn&#8217;t been changed and the using the Fetch as Google too the URL was still &#8220;Not found&#8221;:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2654\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-20-2016.png\" alt=\"fetch-as-google-4-20-2016\" width=\"1149\" height=\"40\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-20-2016.png 1149w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-20-2016-300x10.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-20-2016-768x27.png 768w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-20-2016-1024x36.png 1024w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>Then on\u00a0Saturday\u00a0the Security Issues page indicated that URL injection had been detected as of that day:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2656\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-3.png\" alt=\"security-issues-page-3\" width=\"954\" height=\"410\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-3.png 954w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-3-300x129.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-3-768x330.png 768w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>We again used the Fetch as Google tool and it was still &#8220;Not found&#8221;:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2655\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-23-2016.png\" alt=\"fetch-as-google-4-23-2016\" width=\"1147\" height=\"43\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-23-2016.png 1147w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-23-2016-300x11.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-23-2016-768x29.png 768w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/fetch-as-google-4-23-2016-1024x38.png 1024w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>At this point we also checked the website over to make sure the malicious code hadn&#8217;t returned and it hadn&#8217;t.<\/p>\n<p>Then this morning the warning was gone from the search results and the Security Issues page was clear:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2658\" src=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-4.png\" alt=\"security-issues-page-4\" width=\"1169\" height=\"159\" srcset=\"https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-4.png 1169w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-4-300x41.png 300w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-4-768x104.png 768w, https:\/\/www.whitefirdesign.com\/blog\/wp-content\/uploads\/2016\/04\/security-issues-page-4-1024x139.png 1024w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/p>\n<p>Considering that nothing changed between Saturday and today, that detection on Saturday would seem to be some kind of a mistake. Seeing at the page wasn&#8217;t even being found this doesn&#8217;t seem like an understandable false positive, but something seriously wrong with their system. If you weren&#8217;t aware of that how problematic the process is, you might have been very concerned upon seeing the new false detection.<\/p>\n<p>The fact that it took them a week to finally clear the website also doesn&#8217;t seem to be an acceptable in this case.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Early last year Google changed some of the underlying technology used in their process of of handling\u00a0websites they suspect of being hacked (which leads to a &#8220;This site may be hacked&#8221; message being added to listings for the websites on Google&#8217;s search results). More than a year later\u00a0we are still finding that the review process &hellip; <a href=\"https:\/\/www.whitefirdesign.com\/blog\/2016\/04\/25\/google-needs-to-improve-the-review-process-for-websites-labeled-this-site-may-be-hacked\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Google Needs to Improve the Review Process for Websites Labeled &#8220;This site may be hacked&#8221;&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25,4],"tags":[56],"class_list":["post-2647","post","type-post","status-publish","format-standard","hentry","category-bad-security","category-google","tag-this-site-may-be-hacked"],"_links":{"self":[{"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/posts\/2647","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/comments?post=2647"}],"version-history":[{"count":7,"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/posts\/2647\/revisions"}],"predecessor-version":[{"id":2664,"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/posts\/2647\/revisions\/2664"}],"wp:attachment":[{"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/media?parent=2647"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/categories?post=2647"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whitefirdesign.com\/blog\/wp-json\/wp\/v2\/tags?post=2647"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}