<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Unobfuscating an Attack</title>
	<atom:link href="http://alanp.ca/blog/2010/07/13/unobfuscating-an-attack/feed/" rel="self" type="application/rss+xml" />
	<link>http://alanp.ca/blog/2010/07/13/unobfuscating-an-attack/</link>
	<description>The world, according to alanp</description>
	<lastBuildDate>Mon, 31 Oct 2011 03:23:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Xavier Schott</title>
		<link>http://alanp.ca/blog/2010/07/13/unobfuscating-an-attack/comment-page-1/#comment-2226</link>
		<dc:creator>Xavier Schott</dc:creator>
		<pubDate>Mon, 31 Oct 2011 03:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://alanp.ca/blog/?p=145#comment-2226</guid>
		<description>There are immediate actions you must take when you isolate an attack. The file which led to the infection likely multiplied itself in a few locations.

As described in this article:
http://thegothicparty.com/dev/article/server-side-virus-rat/

you should take serious steps in not only identifying other potential backdoors or RAT, but also tighten the security on your server, starting with ensuring that absolutely no directory is writable, and your WordPress is up-to-date. There are known plug-in security holes, and your first line of response is robust, recent software.</description>
		<content:encoded><![CDATA[<p>There are immediate actions you must take when you isolate an attack. The file which led to the infection likely multiplied itself in a few locations.</p>
<p>As described in this article:<br />
<a href="http://thegothicparty.com/dev/article/server-side-virus-rat/" rel="nofollow">http://thegothicparty.com/dev/article/server-side-virus-rat/</a></p>
<p>you should take serious steps in not only identifying other potential backdoors or RAT, but also tighten the security on your server, starting with ensuring that absolutely no directory is writable, and your WordPress is up-to-date. There are known plug-in security holes, and your first line of response is robust, recent software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erin</title>
		<link>http://alanp.ca/blog/2010/07/13/unobfuscating-an-attack/comment-page-1/#comment-2159</link>
		<dc:creator>Erin</dc:creator>
		<pubDate>Tue, 17 May 2011 14:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://alanp.ca/blog/?p=145#comment-2159</guid>
		<description> This just happened to my wordpress account. I don&#039;t know much about hacks or viruses. I deleted the file (it overtook my style.css file). Is the problem solved now or should I take further action? Thanks!</description>
		<content:encoded><![CDATA[<p> This just happened to my wordpress account. I don&#8217;t know much about hacks or viruses. I deleted the file (it overtook my style.css file). Is the problem solved now or should I take further action? Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wp-popular.com &#187; Blog Archive &#187; Unobfuscating an Attack « alanp.ca : blog</title>
		<link>http://alanp.ca/blog/2010/07/13/unobfuscating-an-attack/comment-page-1/#comment-2124</link>
		<dc:creator>wp-popular.com &#187; Blog Archive &#187; Unobfuscating an Attack « alanp.ca : blog</dc:creator>
		<pubDate>Sun, 25 Jul 2010 08:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://alanp.ca/blog/?p=145#comment-2124</guid>
		<description>[...] post: Unobfuscating an Attack « alanp.ca : blog Tags: code, hack, [...]</description>
		<content:encoded><![CDATA[<p>[...] post: Unobfuscating an Attack « alanp.ca : blog Tags: code, hack, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

