<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Phisher Puts Antiphishing Tool in the Crosshairs</title>
	<atom:link href="http://blog.webroot.com/2010/06/03/phisher-puts-antiphishing-tool-in-the-crosshairs/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.webroot.com/2010/06/03/phisher-puts-antiphishing-tool-in-the-crosshairs/</link>
	<description>WEBROOT - INSIGHTS INTO THREATS AND TRENDS FROM OUR INTERNET SECURITY EXPERTS</description>
	<lastBuildDate>Fri, 17 May 2013 20:44:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: New Bank Phisher Brings Added Functionality, Problems &#171; Webroot Threat Blog</title>
		<link>http://blog.webroot.com/2010/06/03/phisher-puts-antiphishing-tool-in-the-crosshairs/#comment-6007</link>
		<dc:creator><![CDATA[New Bank Phisher Brings Added Functionality, Problems &#171; Webroot Threat Blog]]></dc:creator>
		<pubDate>Wed, 23 Feb 2011 23:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webroot.com/?p=2743#comment-6007</guid>
		<description><![CDATA[[...] installed, so we didn&#8217;t actually see whether the Trojan was successful, but in the past, Trojans that target Rapport were unable to trip up Rapport&#8217;s components, which have a built in self-protection [...]]]></description>
		<content:encoded><![CDATA[<p>[...] installed, so we didn&#8217;t actually see whether the Trojan was successful, but in the past, Trojans that target Rapport were unable to trip up Rapport&#8217;s components, which have a built in self-protection [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
