<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bryan Stephens&#187; Blogging</title>
	<atom:link href="http://bryanjamesstephens.com/category/blogging/feed" rel="self" type="application/rss+xml" />
	<link>http://bryanjamesstephens.com</link>
	<description></description>
	<lastBuildDate>Tue, 06 Dec 2011 00:52:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Malware Notification From Google For A WordPress Blog</title>
		<link>http://bryanjamesstephens.com/internet-marketing/malware-notification-from-google-for-a-wordpress-blog</link>
		<comments>http://bryanjamesstephens.com/internet-marketing/malware-notification-from-google-for-a-wordpress-blog#comments</comments>
		<pubDate>Tue, 06 May 2008 11:49:17 +0000</pubDate>
		<dc:creator>Bryan</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Internet Marketing]]></category>

		<guid isPermaLink="false">http://bryanjamesstephens.com/?p=24</guid>
		<description><![CDATA[I was searching through my mail recently and found an email, written below, with respect to a blog that my dad works on. At first I thought that it was some sort of spam or trick, but after investigating it further I realized that it was for real and there really was a problem. Dear site owner [...]]]></description>
			<content:encoded><![CDATA[<p>I was searching through my mail recently and found an email, written below, with respect to a blog that my dad works on. At first I thought that it was some sort of spam or trick, but after investigating it further I realized that it was for real and there really was a problem.</p>
<blockquote><p>Dear site owner or webmaster of <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://beatyourdepression.com/" target="_blank">beatyourdepression.com</a>,</p>
<p>We recently discovered that some of your pages can cause users to be<br />
infected with malicious software. We have begun showing a warning page<br />
to users who visit these pages by clicking a search result on Google.com.<br />
Below are some example URLs on your site which can cause users to be<br />
infected (space inserted to prevent accidental clicking in case your<br />
mail client auto-links URLs):</p>
<p>http://beatyourdepression .com/blog/<br />
http://beatyourdepression .com/blog/category/overcoming-depression</p>
<p>Here is a link to a sample warning page:<br />
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.google.com/interstitial?url=http%3A//beatyourdepression.com/blog/" target="_blank">http://www.google.com/interstitial?url=http%3A//beatyourdepression.com/blog/</a></p>
<p>We strongly encourage you to investigate this immediately to protect<br />
your visitors. Although some sites intentionally distribute malicious<br />
software, in many cases the webmaster is unaware because:</p>
<p>1) the site was compromised<br />
2) the site doesn&#8217;t monitor for malicious user-contributed content<br />
3) the site displays content from an ad network that has a malicious<br />
advertiser</p>
<p>If your site was compromised, it&#8217;s important to not only remove the<br />
malicious (and usually hidden) content from your pages, but to also<br />
identify and fix the vulnerability. We suggest contacting your hosting<br />
provider if you are unsure of how to proceed. StopBadware also has a<br />
resource page for securing compromised sites:<br />
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.stopbadware.org/home/security" target="_blank"><script type="text/javascript"></script>http://www.stopbadware.org/home/security</a></p>
<p>Once you&#8217;ve secured your site, you can request that the warning be<br />
removed by visiting<br />
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.google.com/support/webmasters/bin/answer.py?answer=45432" target="_blank">http://www.google.com/support/webmasters/bin/answer.py?answer=45432</a><br />
and requesting a review. If your site is no longer harmful to users,<br />
we will remove the warning.</p>
<p>Sincerely,<br />
<span class="sg"><span style="color: #888888;">Google Search Quality Team</span></span></p></blockquote>
<p> </p>
<p>I checked out some information from stopbadware.com and realized that the static site was OK, but the blog had some problems. I now know why the traffic stats had dropped significantly. Google had dropped the blog posts from its index.</p>
<p>I contacted my hosting company. They were helpful as usual, but they told me that they could not really help me too much without any more specific information from Google.</p>
<p>I knew that dad and I had not deliberately put malicious content on the blog, so I investigated further by checking <a title="Clearing House" href="http://www.stopbadware.org/home/reportsearch" target="_blank">http://www.stopbadware.org/home/reportsearch</a><a title="Clearing House" href="http://www.stopbadware.org/home/clearinghouse" target="_blank"></a> with all of the external links that we had on the blog. All of them were found to be clean.</p>
<p>I used the clearing house tool with several of my other sites, including this blog, and they all came up clean until I arrived to another site with the same wordpress theme as the beatyourdepression theme. Therefore I thought that it was possible that the theme itself had been corrupted somehow. However, I found some other sites with the same wordpress them and they all were clear.</p>
<p>I then tried some of my other blogs and found a few more that were earmarked by the clearing house as having badware within them.</p>
<p>It then became apparent that there was a common denominator between the blogs that had badware and those that were OK. The ones that had badware had &#8220;Anyone can register&#8221; ticked in the membership section of the settings in wordpress. I unticked all of those boxes on the affected sites, although the latest wordpress upgrade (2.5.1) is supposed to fix this problem.</p>
<p>I then had to search through all of the posts for coding that was not supposed to be there. (Go to Manage post and choose html). Much of the bad coding had iframes and something like &#8220;&lt;-traffic Statistics&#8221; and links to bad sites such as ringphones, casinos etc. It took ages to sift through all of the posts and remove all of the bad code, but hopefully it is all OK now. Note that all of the badware is not visible on your blog for the viewer.</p>
<p>I have asked for Google and stopbadware to check the site out again and I shall have to wait and see how it all goes. I really have to thank them for alerting me about the badware as the last thing I would like is having my readers being affected by it.</p>
<p>I have learnt my lessons. </p>
<p>So what do I suggest other bloggers to do right now???</p>
<ol>
<li>Upgrade your wordpress (or other type) blog NOW.</li>
<li>Remove the tick from &#8220;Anyone can register&#8221; if that is not totally necessary.</li>
<li>Check out to see if your sites have badware on them using <a href="http://www.stopbadware.org/home/reportsearch" target="_blank">http://www.stopbadware.org/home/reportsearch</a></li>
<li>Fix up any corrupt posts or pages by deleting the bad code</li>
<li>Tell Google and Stopbadware that your site is now OK again (if there was a problem in the 1st place)</li>
<li>Have a nice cup of tea and keep a positive attitude <img src='http://bryanjamesstephens.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
 </li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://bryanjamesstephens.com/internet-marketing/malware-notification-from-google-for-a-wordpress-blog/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

