<?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"
	>
<channel>
	<title>Comments on: Multiple Popular Websites Affected By EyeWonder Malware Incident</title>
	<atom:link href="http://cyberinsecure.com/multiple-popular-websites-affected-by-eyewonder-malware-incident/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyberinsecure.com/multiple-popular-websites-affected-by-eyewonder-malware-incident/</link>
	<description>Daily cyber threats and internet security news: network security, online safety and latest security alerts</description>
	<pubDate>Thu, 18 Mar 2010 22:32:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: hifi</title>
		<link>http://cyberinsecure.com/multiple-popular-websites-affected-by-eyewonder-malware-incident/#comment-1455</link>
		<dc:creator>hifi</dc:creator>
		<pubDate>Sun, 05 Jul 2009 03:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://cyberinsecure.com/?p=1382#comment-1455</guid>
		<description>Apparently, the exploit only affected the home page www.eyewonder.com and not any advertising, which was hosted on a different server (which can be verified by traceroutes). The warnings on other sites were simply because Google flagged *.eyewonder.com

It looks like Eyewonder has fixed the issue caused by the hack into Coldfusion on their home page and Google has unflagged them.</description>
		<content:encoded><![CDATA[<p>Apparently, the exploit only affected the home page <a href="http://www.eyewonder.com" rel="nofollow">http://www.eyewonder.com</a> and not any advertising, which was hosted on a different server (which can be verified by traceroutes). The warnings on other sites were simply because Google flagged *.eyewonder.com</p>
<p>It looks like Eyewonder has fixed the issue caused by the hack into Coldfusion on their home page and Google has unflagged them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
