<?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: If your site has been compromised with phishing attack code&#8230;</title>
	<atom:link href="http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/</link>
	<description>The world through my prisms</description>
	<lastBuildDate>Tue, 07 Sep 2010 21:11:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Do Not Use Nulled Scripts or Templates - Dntist.Net</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-416</link>
		<dc:creator>Do Not Use Nulled Scripts or Templates - Dntist.Net</dc:creator>
		<pubDate>Thu, 25 Mar 2010 02:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-416</guid>
		<description>[...] Now this code can be linked with any sites giving your site bad neighborhood links that can have a negative effect on your rankings on Google and other search engines. Moreover your site can be compromised with phishing attack code&#8230;.. [...]</description>
		<content:encoded><![CDATA[<p>[...] Now this code can be linked with any sites giving your site bad neighborhood links that can have a negative effect on your rankings on Google and other search engines. Moreover your site can be compromised with phishing attack code&#8230;.. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hawaiian Joe</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-415</link>
		<dc:creator>Hawaiian Joe</dc:creator>
		<pubDate>Sat, 20 Feb 2010 18:40:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-415</guid>
		<description>http://www.surbl.org/ is another site to make sure your site isn&#039;t on the spam/phishing black list. If it is they will remove it pretty fast if you report it there.</description>
		<content:encoded><![CDATA[<p><a href="http://www.surbl.org/" rel="nofollow">http://www.surbl.org/</a> is another site to make sure your site isn&#8217;t on the spam/phishing black list. If it is they will remove it pretty fast if you report it there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aneesh</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-346</link>
		<dc:creator>Aneesh</dc:creator>
		<pubDate>Wed, 13 Jan 2010 06:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-346</guid>
		<description>step 1 : change FTP password
Step 2 : Download all files and clean
Step 3 : upload Files
Step 4 : Set 444 permission to all files, except Custom Upload folders

Remeber Do not save FTP password in  your FTP client
If you suspects that your system is infected, Format and install OS, then install a good antivirus + firewall. I suggest Avast free edition and Comodo Firewall.

We have received many inquiries and we cleaned those infected sites. If your site is infected Please contact us

Best Regards,
Team HelloSystemadmin.com</description>
		<content:encoded><![CDATA[<p>step 1 : change FTP password<br />
Step 2 : Download all files and clean<br />
Step 3 : upload Files<br />
Step 4 : Set 444 permission to all files, except Custom Upload folders</p>
<p>Remeber Do not save FTP password in  your FTP client<br />
If you suspects that your system is infected, Format and install OS, then install a good antivirus + firewall. I suggest Avast free edition and Comodo Firewall.</p>
<p>We have received many inquiries and we cleaned those infected sites. If your site is infected Please contact us</p>
<p>Best Regards,<br />
Team HelloSystemadmin.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trish</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-317</link>
		<dc:creator>Trish</dc:creator>
		<pubDate>Sun, 18 Oct 2009 20:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-317</guid>
		<description>Thank you for your post, it was extremely helpful! This same exact issue just happened to me last week -- Wachovia bank security aler. I am now unable to send my URL to anyone through email due to the phishing attack code now logged with my site. I know nothing about how you fixed it, but I will forward your link to my web people. I am still dealing with the clean-up. I now think that I have a trojan or some other kind of spyware on my Mac, as many &quot;phishy&quot; things continue to occur that make me suspicious. Thank you again.</description>
		<content:encoded><![CDATA[<p>Thank you for your post, it was extremely helpful! This same exact issue just happened to me last week &#8212; Wachovia bank security aler. I am now unable to send my URL to anyone through email due to the phishing attack code now logged with my site. I know nothing about how you fixed it, but I will forward your link to my web people. I am still dealing with the clean-up. I now think that I have a trojan or some other kind of spyware on my Mac, as many &#8220;phishy&#8221; things continue to occur that make me suspicious. Thank you again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moonjungle</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-289</link>
		<dc:creator>moonjungle</dc:creator>
		<pubDate>Wed, 18 Mar 2009 06:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-289</guid>
		<description>Hey man this definitely useful info.</description>
		<content:encoded><![CDATA[<p>Hey man this definitely useful info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Semantic Overload</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-288</link>
		<dc:creator>Semantic Overload</dc:creator>
		<pubDate>Wed, 18 Mar 2009 03:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-288</guid>
		<description>@patrix That&#039;s a great question! Honestly, there is no foolproof mechanism to do that. Often, the CMS engines you use themselves have security vulnerabilities that are often exploited by hackers to insert such malicious code.
Having said that, there are mechanisms to mitigate the vulnerabilities, but they come with a price. For instance, you can give read-and-execute only permissions to all your files and directories. This ensures that the hackers don&#039;t have the requisite permissions to install such code. But that means that you can&#039;t upload images or do automatic upgrades from the front-end. So everytime you want to &#039;write&#039; (or add or modify) any file to your website from the browser you will have to temporarily give write permissions to the necessary files and directories and then revert the permissions back after you are done.

So, in short, there is no guaranteed mechanism to prevent such attacks. Like I mentioned towards the end of this post: it&#039;s a cat-and-mouse game that the CMS developers and website owners play with hackers, with each group trying to outdo the other. Sorry, I couldn&#039;t be more helpful regarding this. Perhaps an expert on network and web security could provide a more insightful commmentery on it.</description>
		<content:encoded><![CDATA[<p>@patrix That&#8217;s a great question! Honestly, there is no foolproof mechanism to do that. Often, the CMS engines you use themselves have security vulnerabilities that are often exploited by hackers to insert such malicious code.<br />
Having said that, there are mechanisms to mitigate the vulnerabilities, but they come with a price. For instance, you can give read-and-execute only permissions to all your files and directories. This ensures that the hackers don&#8217;t have the requisite permissions to install such code. But that means that you can&#8217;t upload images or do automatic upgrades from the front-end. So everytime you want to &#8216;write&#8217; (or add or modify) any file to your website from the browser you will have to temporarily give write permissions to the necessary files and directories and then revert the permissions back after you are done.</p>
<p>So, in short, there is no guaranteed mechanism to prevent such attacks. Like I mentioned towards the end of this post: it&#8217;s a cat-and-mouse game that the CMS developers and website owners play with hackers, with each group trying to outdo the other. Sorry, I couldn&#8217;t be more helpful regarding this. Perhaps an expert on network and web security could provide a more insightful commmentery on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrix</title>
		<link>http://www.semanticoverload.com/2009/03/17/if-your-site-has-been-compromised-with-phishing-attack-code/comment-page-1/#comment-287</link>
		<dc:creator>Patrix</dc:creator>
		<pubDate>Tue, 17 Mar 2009 16:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.semanticoverload.com/?p=316#comment-287</guid>
		<description>You&#039;re lucky you were at least informed by Wachovia. How do we prevent them from inserting such malicious code in the first place?</description>
		<content:encoded><![CDATA[<p>You&#8217;re lucky you were at least informed by Wachovia. How do we prevent them from inserting such malicious code in the first place?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
