<?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>Free Technology Tutorials &#187; WordPress Hacked</title>
	<atom:link href="http://educhalk.org/blog/tag/wordpress-hacked/feed/" rel="self" type="application/rss+xml" />
	<link>http://educhalk.org/blog</link>
	<description>Technology Made Easy</description>
	<lastBuildDate>Mon, 06 Sep 2010 20:44:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>WordPress Blog Hacked &#8212; Now What?</title>
		<link>http://educhalk.org/blog/wordpress-blog-hacked-now-what/</link>
		<comments>http://educhalk.org/blog/wordpress-blog-hacked-now-what/#comments</comments>
		<pubDate>Sat, 23 Jan 2010 15:46:24 +0000</pubDate>
		<dc:creator>figaro</dc:creator>
				<category><![CDATA[From WordPress Codex -- GPL]]></category>
		<category><![CDATA[WP General]]></category>
		<category><![CDATA[From WordPress Codex]]></category>
		<category><![CDATA[Hacked]]></category>
		<category><![CDATA[WordPress Hacked]]></category>

		<guid isPermaLink="false">http://educhalk.org/blog/?p=753</guid>
		<description><![CDATA[Note: The following is made available under GPL from http://codex.wordpress.org/GPL. It has been edited significantly from its original form. There is no guarantee this information is accurate&#8230;use at your own risk. &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211; My WordPress blog has been hacked; or at least I think its been hacked. What do I do now? The WordPress Exploit Scanner [...]


Related posts:<ol><li><a href='http://educhalk.org/blog/wordpress-tip-delete-old-or-unwanted-plugins/' rel='bookmark' title='Permanent Link: WordPress Tip: Delete Old or Unwanted Plugins'>WordPress Tip: Delete Old or Unwanted Plugins</a> <small>Note: The following is made available under GPL from http://codex.wordpress.org/GPL....</small></li>
<li><a href='http://educhalk.org/blog/easy-5-step-wordpress-install/' rel='bookmark' title='Permanent Link: Easy 5-Step WordPress Install'>Easy 5-Step WordPress Install</a> <small>Note: The following is made available under GPL from http://codex.wordpress.org/GPL....</small></li>
<li><a href='http://educhalk.org/blog/resetting-your-wordpress-password/' rel='bookmark' title='Permanent Link: Resetting Your WordPress Password'>Resetting Your WordPress Password</a> <small>Note: The following is made available under GPL from http://codex.wordpress.org/GPL....</small></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p><em>Note: The following is made available under GPL from http://codex.wordpress.org/GPL. It has been edited significantly from its original form. There is no guarantee this information is accurate&#8230;use at your own risk.</em><br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p><strong>My WordPress blog has been hacked; or at least I think its been hacked. What do I do now?</strong></p>
<p>The WordPress <a href="http://wordpress.org/extend/plugins/exploit-scanner/" target="_blank">Exploit Scanner</a> plugin can help detect damage so that it can be cleaned up. Other things you should do:</p>
<ul>
<li>Change passwords for all blog users, including your own, with a role higher than Subscriber</li>
<li>If you upload files to your site via FTP, change your FTP password</li>
<li>Change your web hosting control panel (such as Cpanel) password</li>
<li>Completely remove all current WordPress core code and re-install the latest version of WordPress</li>
<li>Make sure you are only using trusted plugins and themes&#8211;those from wordpress.org or a trusted commercial developer</li>
<li>Remove all unused themes and plugins</li>
<li>Make sure all of your plugins and themes are up-to-date&#8211;it&#8217;s best to install new, clean copies of each theme and plugin</li>
<li>Update your security keys in wp-config.php</li>
<li>Search your entire web-directory (public_html directory, not just the WP directory) to ensure no other files are infected</li>
<li>Check directory and file permission on your server. Typically, directory permissions should be 755 and files should be 644, but this will depend on your particular server environment.</li>
</ul>
<p>If all else fails, <a href="http://educhalk.org/blog/contact/">contact me</a> and I will quote you a reasonable price for fixing your site for you&#8230;I only work on Linux systems with Cpanel, or an equivalent control panel.</p>


<p>Related posts:<ol><li><a href='http://educhalk.org/blog/wordpress-tip-delete-old-or-unwanted-plugins/' rel='bookmark' title='Permanent Link: WordPress Tip: Delete Old or Unwanted Plugins'>WordPress Tip: Delete Old or Unwanted Plugins</a> <small>Note: The following is made available under GPL from http://codex.wordpress.org/GPL....</small></li>
<li><a href='http://educhalk.org/blog/easy-5-step-wordpress-install/' rel='bookmark' title='Permanent Link: Easy 5-Step WordPress Install'>Easy 5-Step WordPress Install</a> <small>Note: The following is made available under GPL from http://codex.wordpress.org/GPL....</small></li>
<li><a href='http://educhalk.org/blog/resetting-your-wordpress-password/' rel='bookmark' title='Permanent Link: Resetting Your WordPress Password'>Resetting Your WordPress Password</a> <small>Note: The following is made available under GPL from http://codex.wordpress.org/GPL....</small></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://educhalk.org/blog/wordpress-blog-hacked-now-what/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
