<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The FORWARD project blog &#187; worm</title>
	<atom:link href="http://blogs.ict-forward.eu/forward/tag/worm/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ict-forward.eu/forward</link>
	<description>blogging on emerging and future threats</description>
	<lastBuildDate>Mon, 30 Jan 2012 09:09:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Twitter worm strikes again</title>
		<link>http://blogs.ict-forward.eu/forward/twitter-worm-strikes-again/</link>
		<comments>http://blogs.ict-forward.eu/forward/twitter-worm-strikes-again/#comments</comments>
		<pubDate>Tue, 28 Apr 2009 11:22:56 +0000</pubDate>
		<dc:creator>zarras</dc:creator>
				<category><![CDATA[security news]]></category>
		<category><![CDATA[mikey]]></category>
		<category><![CDATA[mooney]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://blogs.ict-forward.eu/forward/?p=135</guid>
		<description><![CDATA[Almost a week ago since its first release, a new worm hit the twitter again. The first attack happened during Easter when twitter was hit by powerful, self-replicating attacks that caused people to flood the micro-blogging site with tens of thousands of messages simply by viewing booby trapped user profiles. The second worm, which began [...]]]></description>
			<content:encoded><![CDATA[<p>Almost a week ago since its first release, a new worm hit the twitter again. The first attack happened during Easter when twitter was hit by powerful, self-replicating attacks that caused people to flood the micro-blogging site with tens of thousands of messages simply by viewing booby trapped user profiles.</p>
<p><span id="more-135"></span>The second worm, which began spreading on Friday ( 6 days after first worm ), referenced Twitter users with a large number of followers (such as @oprah, Oprah Winfrey, and @aplus, Ashton Kutcher). A day later, on Saturday, two more worms appeared, featuring philosophical musings and the word &#8220;womp&#8221;. The second worm of the day screwed with infected profiles, changing the title of the profile to &#8220;Mikey and the Mysterious Treqz&#8221;, as explained in a blog post by <a href="http://www.f-secure.com/weblog/archives/00001662.html">F-Secure</a>.</p>
<p>The creator of said worms is Mikey Mooney, again! Mikey is 17 years old and claimed responsibility for releasing the first worm, citing boredom. According to Mikey the latest variant aimed to prove that Twitter did not fix the cross site scripting flaw that supposedly was taken care of , according to <a href="http://blogs.zdnet.com/security/?p=3125">ZDNet</a>. After releasing the first worm Mikey had landed a job as a web applications developer at <a href="http://exqsoft.com">exqSoft Solutions</a>. Despite this, Mikey&#8217;s latest actions show that outfronting exploits to the community, albeit in a &#8220;brute&#8221; manner, is still amongst his interests.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ict-forward.eu/forward/twitter-worm-strikes-again/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The day has come!</title>
		<link>http://blogs.ict-forward.eu/forward/the-day-has-come/</link>
		<comments>http://blogs.ict-forward.eu/forward/the-day-has-come/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 00:04:49 +0000</pubDate>
		<dc:creator>Spyros Ligouras</dc:creator>
				<category><![CDATA[security news]]></category>
		<category><![CDATA[conficker]]></category>
		<category><![CDATA[f-secure]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://blogs.ict-forward.eu/forward/?p=100</guid>
		<description><![CDATA[Today, April 1 2009 is the alleged Doomsday of the Conficker/Downadup worm activation. Conficker has lately been under the spotlight of many well known tech blogs and even news websites garnering lots of attention. Even Conficker fanpages have been created in popular social networking sites. Now that it&#8217;s here disappointment might strike the masses as [...]]]></description>
			<content:encoded><![CDATA[<p>Today, April 1 2009 is the alleged Doomsday of the Conficker/Downadup worm activation. Conficker has lately been under the spotlight of many well known <a href="http://www.pcmag.com/article2/0,2817,2343910,00.asp">tech blogs</a> and even <a href="http://www.cbsnews.com/stories/2009/03/27/60minutes/main4897053.shtml">news websites</a> garnering lots of attention.  Even Conficker fanpages have been created in popular social networking sites. Now that it&#8217;s here disappointment might  strike the masses as reportedly &#8220;<a href="http://www.f-secure.com/weblog/archives/00001643.html"><span class="rss:item">Conficker has activated. So far nothing has actually happened.</span></a>&#8221;  Still there&#8217;s plenty of time ahead, and since not all of the worm&#8217;s behavior is known there might be a surprise ahead for us.</p>
<p><span id="more-100"></span>The people at <a href="http://www.f-secure.com">F-Secure</a> have uploaded a presentation about Conficker on Youtube. Follow the links below to watch it.</p>
<p><a href="http://www.youtube.com/watch?v=eoAYsGV5MkY"> Case Conficker &#8211; Part 1</a></p>
<p><a href="http://www.youtube.com/watch?v=9Zr-nE74VQc"> Case Conficker &#8211; Part 2</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.ict-forward.eu/forward/the-day-has-come/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

