<?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: TuxTweaks Got Hacked</title>
	<atom:link href="http://tuxtweaks.com/2009/10/tuxtweaks-got-hacked/feed/" rel="self" type="application/rss+xml" />
	<link>http://tuxtweaks.com/2009/10/tuxtweaks-got-hacked/</link>
	<description>Linux Tweaks, HowTo&#039;s and Reviews</description>
	<lastBuildDate>Mon, 21 May 2012 13:40:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Linerd</title>
		<link>http://tuxtweaks.com/2009/10/tuxtweaks-got-hacked/comment-page-1/#comment-979</link>
		<dc:creator>Linerd</dc:creator>
		<pubDate>Sun, 18 Oct 2009 04:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://tuxtweaks.com/?p=931#comment-979</guid>
		<description>Well, if it was a problem with my site, it was an exploit in WordPress 2.8.4. I upgraded the site to 2.8.4 in August and my site got hacked on Sept. 11. It seems like more than coincidence that 9 out of 10 sites I found showing the same problem were all with Inmotion. BTW, it&#039;s been reported on Drupal sites as well. 

Perhaps it&#039;s my fault for not changing my cPanel password since signing up. Account login information was included in the site activation email, so if someone got into the sent mail at Inmotion they would have several ID&#039;s and passwords.

The disappointing thing is that Inmotion knew that there was an issue. They could have run a simple
&lt;div class=&quot;term&quot;&gt;rgrep 2309h34b34b34b *&lt;/div&gt;
on each of their servers and found all the hacked accounts. It wouldn&#039;t have been too much to ask to send out an email to the affected account holders letting them know of the problem and their proposed solution. Instead, they chose to simply deny any responsibility and left their customers to discover the problem on their own.</description>
		<content:encoded><![CDATA[<p>Well, if it was a problem with my site, it was an exploit in WordPress 2.8.4. I upgraded the site to 2.8.4 in August and my site got hacked on Sept. 11. It seems like more than coincidence that 9 out of 10 sites I found showing the same problem were all with Inmotion. BTW, it's been reported on Drupal sites as well. </p>
<p>Perhaps it's my fault for not changing my cPanel password since signing up. Account login information was included in the site activation email, so if someone got into the sent mail at Inmotion they would have several ID's and passwords.</p>
<p>The disappointing thing is that Inmotion knew that there was an issue. They could have run a simple</p>
<div class="term">rgrep 2309h34b34b34b *</div>
<p>on each of their servers and found all the hacked accounts. It wouldn't have been too much to ask to send out an email to the affected account holders letting them know of the problem and their proposed solution. Instead, they chose to simply deny any responsibility and left their customers to discover the problem on their own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://tuxtweaks.com/2009/10/tuxtweaks-got-hacked/comment-page-1/#comment-963</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 17 Oct 2009 21:50:37 +0000</pubDate>
		<guid isPermaLink="false">http://tuxtweaks.com/?p=931#comment-963</guid>
		<description>The same thing happened to me but I&#039;m hosting with Hostgater not Inmotion.  The search you showed though doesnt seem like its all the same kind of problem. With  mine Hostgator showed me the logs and I saw that the problem was an exploit in Wordpress 2.8.3.  When I upgraded Wordpress and changed my FTP password I never had this problem again. Sorry man but the problem is your site not your host.</description>
		<content:encoded><![CDATA[<p>The same thing happened to me but I'm hosting with Hostgater not Inmotion.  The search you showed though doesnt seem like its all the same kind of problem. With  mine Hostgator showed me the logs and I saw that the problem was an exploit in WordPress 2.8.3.  When I upgraded WordPress and changed my FTP password I never had this problem again. Sorry man but the problem is your site not your host.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

