<?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 for Think Affiliate</title>
	<atom:link href="http://www.thinkaffiliate.co.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkaffiliate.co.uk</link>
	<description>Build Your Online Revenue Stream</description>
	<lastBuildDate>Fri, 07 Aug 2009 06:37:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Web Hosting and Domain Names by Samantha</title>
		<link>http://www.thinkaffiliate.co.uk/web-hosting-and-domain-names/28/comment-page-1/#comment-20</link>
		<dc:creator>Samantha</dc:creator>
		<pubDate>Fri, 07 Aug 2009 06:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=28#comment-20</guid>
		<description>Selling products as an domain reseller is a great way to make money. For one thing, you get to earn money from the products without having to fulfill them yourself or deal with customer service issues. Nothing is better than that! The returns are usually higher than with Adsense, provided you’re able to find an offer that converts well with the people who visit your website.

Here is some caution we all need to look out for!!

The beautiful thing about a good domain name is that every domain name is unique and can be a sustainable competitive advantage even for the “little guy”. 
    But beware, I do put a word of caution out into the community that there are a lot of registrars that when you type in the name to see if it is taken, they immediately register it for themselves (if you don’t). This is a disgusting practice.

When I started blogging I never really thought of buying my own domain. I just wanted to write and blog all my ideas, aspirations, dreams and anything that are happening to me.
          Plain and simple, isn&#039;t it?

For A long time no but now things are moving on smoother then ever. Just passing on this Info to anyone who is interested. Thanks</description>
		<content:encoded><![CDATA[<p>Selling products as an domain reseller is a great way to make money. For one thing, you get to earn money from the products without having to fulfill them yourself or deal with customer service issues. Nothing is better than that! The returns are usually higher than with Adsense, provided you’re able to find an offer that converts well with the people who visit your website.</p>
<p>Here is some caution we all need to look out for!!</p>
<p>The beautiful thing about a good domain name is that every domain name is unique and can be a sustainable competitive advantage even for the “little guy”.<br />
    But beware, I do put a word of caution out into the community that there are a lot of registrars that when you type in the name to see if it is taken, they immediately register it for themselves (if you don’t). This is a disgusting practice.</p>
<p>When I started blogging I never really thought of buying my own domain. I just wanted to write and blog all my ideas, aspirations, dreams and anything that are happening to me.<br />
          Plain and simple, isn&#8217;t it?</p>
<p>For A long time no but now things are moving on smoother then ever. Just passing on this Info to anyone who is interested. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by admin</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-19</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 05 Aug 2009 12:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-19</guid>
		<description>I found a Trojan on my work laptop which I believe was responsible as well. You need to clean the machine(s) you have the FTP passwords saved on before changing the passwords.</description>
		<content:encoded><![CDATA[<p>I found a Trojan on my work laptop which I believe was responsible as well. You need to clean the machine(s) you have the FTP passwords saved on before changing the passwords.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by Les</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-18</link>
		<dc:creator>Les</dc:creator>
		<pubDate>Sat, 01 Aug 2009 09:08:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-18</guid>
		<description>Hi,

We just had 20 sites Edit with http://x9y.ru:8080/ts/in.cgi?pepsi120 within 5 mintues, and on 8 diffrent servers. We tracked it down to a infected laptop in the office and it used cute FTP. We removed the laptop and fixed all the sites and changes the password on 19 sites left one test site with the same password, plug the laptop back in and within 2 mins of opening cute ftp the site was edited with the code. 

The good news was we found the problem :) the bad news was it spread to to other computers on the network.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>We just had 20 sites Edit with <a href="http://x9y.ru:8080/ts/in.cgi?pepsi120" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/x9y.ru_8080/ts/in.cgi?pepsi120&amp;referer=');">http://x9y.ru:8080/ts/in.cgi?pepsi120</a> within 5 mintues, and on 8 diffrent servers. We tracked it down to a infected laptop in the office and it used cute FTP. We removed the laptop and fixed all the sites and changes the password on 19 sites left one test site with the same password, plug the laptop back in and within 2 mins of opening cute ftp the site was edited with the code. </p>
<p>The good news was we found the problem <img src='http://www.thinkaffiliate.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  the bad news was it spread to to other computers on the network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by admin</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-17</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 30 Jul 2009 06:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-17</guid>
		<description>Also, it is NOT a brute force attack as FTP logs show they got the password right first time. Probably a good idea to scan for trojan horses on your own machine.</description>
		<content:encoded><![CDATA[<p>Also, it is NOT a brute force attack as FTP logs show they got the password right first time. Probably a good idea to scan for trojan horses on your own machine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by admin</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-16</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 30 Jul 2009 06:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-16</guid>
		<description>I was told that it was probably the FTP which had been compromised and that all passwords should be changed. This fits as the sites with different FTP passwords were not affected.</description>
		<content:encoded><![CDATA[<p>I was told that it was probably the FTP which had been compromised and that all passwords should be changed. This fits as the sites with different FTP passwords were not affected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by Gsp</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-15</link>
		<dc:creator>Gsp</dc:creator>
		<pubDate>Mon, 27 Jul 2009 12:34:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-15</guid>
		<description>I had the same problem yesterday with some sites, The easy solution is to delete the iframe lines, but the pages can be infected again, someone know how to close the backdoor?

thanks</description>
		<content:encoded><![CDATA[<p>I had the same problem yesterday with some sites, The easy solution is to delete the iframe lines, but the pages can be infected again, someone know how to close the backdoor?</p>
<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by Ayolt Talen</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-14</link>
		<dc:creator>Ayolt Talen</dc:creator>
		<pubDate>Mon, 13 Jul 2009 11:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-14</guid>
		<description>Dear Vincent, we&#039;re having the same at this moment. Since friday, 4 of our servers have been attacked. The content of the page that is called in the iframe appears to contain a virus, so be carefull!

In our case, I could just search in windows for all files named &#039;index.&#039; and &#039;default.&#039; that had been changed in the past few days. In there, I found that they append the iframe-code right after the BODY-tag or at the end of the file if there is no bodytag.

I have been trying to find what is the vulnerability that let&#039;s them in. Do you have any idea? We had the problem on a windows2000 machine with IIS and ColdFusion 5.0, MS SQL server 7. But we also had it on a newer machine with windows2003x64 with IIS and Coldfusion 7MX and SQL server 2005.

Did you find anything so far? Please let me know what type of machine you&#039;re using. 

Best regards and thanks,
Ayolt</description>
		<content:encoded><![CDATA[<p>Dear Vincent, we&#8217;re having the same at this moment. Since friday, 4 of our servers have been attacked. The content of the page that is called in the iframe appears to contain a virus, so be carefull!</p>
<p>In our case, I could just search in windows for all files named &#8216;index.&#8217; and &#8216;default.&#8217; that had been changed in the past few days. In there, I found that they append the iframe-code right after the BODY-tag or at the end of the file if there is no bodytag.</p>
<p>I have been trying to find what is the vulnerability that let&#8217;s them in. Do you have any idea? We had the problem on a windows2000 machine with IIS and ColdFusion 5.0, MS SQL server 7. But we also had it on a newer machine with windows2003&#215;64 with IIS and Coldfusion 7MX and SQL server 2005.</p>
<p>Did you find anything so far? Please let me know what type of machine you&#8217;re using. </p>
<p>Best regards and thanks,<br />
Ayolt</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by admin</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-13</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 10 Jul 2009 09:42:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-13</guid>
		<description>I believe it is all &#039;index&#039; and &#039;default&#039; pages affected. Look for ALL of these pages on your site. So if any files are called index and default re-upload them.</description>
		<content:encoded><![CDATA[<p>I believe it is all &#8216;index&#8217; and &#8216;default&#8217; pages affected. Look for ALL of these pages on your site. So if any files are called index and default re-upload them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on http://a3l.ru:8080/ts/in.cgi?pepsi85 by Vincent Huybrechts</title>
		<link>http://www.thinkaffiliate.co.uk/httpa3lru8080tsincgipepsi85/91/comment-page-1/#comment-12</link>
		<dc:creator>Vincent Huybrechts</dc:creator>
		<pubDate>Thu, 02 Jul 2009 22:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=91#comment-12</guid>
		<description>Hi,

Today I noticed the same code is appearing at the bottom of my wordpress powered site too. I re-uploaded all the wordpress files, including my theme. But the iframe is still there. And I really can&#039;t find anything wrong in a file. 

My site: www.startgrid.be (there&#039;s a space between the bottom of the content and the bottom of the browserwindow wich isn&#039;t supposed to be there.)

You say you deleted the affected files, can you tell me which files that were in your case ?

Thanks,
Vincent</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Today I noticed the same code is appearing at the bottom of my wordpress powered site too. I re-uploaded all the wordpress files, including my theme. But the iframe is still there. And I really can&#8217;t find anything wrong in a file. </p>
<p>My site: <a href="http://www.startgrid.be" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.startgrid.be?referer=');">http://www.startgrid.be</a> (there&#8217;s a space between the bottom of the content and the bottom of the browserwindow wich isn&#8217;t supposed to be there.)</p>
<p>You say you deleted the affected files, can you tell me which files that were in your case ?</p>
<p>Thanks,<br />
Vincent</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on This Site May Harm Your Computer by Mkcoy</title>
		<link>http://www.thinkaffiliate.co.uk/this-site-may-harm-your-computer/87/comment-page-1/#comment-11</link>
		<dc:creator>Mkcoy</dc:creator>
		<pubDate>Thu, 21 May 2009 16:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkaffiliate.co.uk/?p=87#comment-11</guid>
		<description>Well they have said that they will &quot;put more robust file checks in place to prevent it from happening again&quot;. However a lot of people would have lost out on profits because of this. Even if it was only 40 minutes. And Google are hardly likely to recompensate them. This is a blatent human error of course and these things do happen. But that shouldn&#039;t be an excuse for it. God forbid this ever happen again!</description>
		<content:encoded><![CDATA[<p>Well they have said that they will &#8220;put more robust file checks in place to prevent it from happening again&#8221;. However a lot of people would have lost out on profits because of this. Even if it was only 40 minutes. And Google are hardly likely to recompensate them. This is a blatent human error of course and these things do happen. But that shouldn&#8217;t be an excuse for it. God forbid this ever happen again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
