<?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: Twitter: Target of a Not-so-Normal DDoS Attack?</title>
	<atom:link href="http://blog.trendmicro.com/twitter-target-of-a-not-so-normal-ddos-attack/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.trendmicro.com/twitter-target-of-a-not-so-normal-ddos-attack/</link>
	<description>Threat News and Information Direct from the Experts</description>
	<lastBuildDate>Fri, 10 Feb 2012 02:16:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Kdecherf (Kevin Decherf)</title>
		<link>http://blog.trendmicro.com/twitter-target-of-a-not-so-normal-ddos-attack/comment-page-1/#comment-31564</link>
		<dc:creator>Kdecherf (Kevin Decherf)</dc:creator>
		<pubDate>Tue, 11 Aug 2009 17:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.trendmicro.com/?p=18695#comment-31564</guid>
		<description>RT &lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/TrendMicro&quot;&gt;@TrendMicro&lt;/a&gt;: Twitter: Target of a Not-so-Normal DDoS Attack? http://blog.trendmicro.com/?p=18695</description>
		<content:encoded><![CDATA[<p>RT <a rel="nofollow" href="http://twitter.com/TrendMicro">@TrendMicro</a>: Twitter: Target of a Not-so-Normal DDoS Attack? <a href="http://blog.trendmicro.com/?p=18695" rel="nofollow">http://blog.trendmicro.com/?p=18695</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TrendMicro (TrendMicro)</title>
		<link>http://blog.trendmicro.com/twitter-target-of-a-not-so-normal-ddos-attack/comment-page-1/#comment-31563</link>
		<dc:creator>TrendMicro (TrendMicro)</dc:creator>
		<pubDate>Tue, 11 Aug 2009 16:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.trendmicro.com/?p=18695#comment-31563</guid>
		<description>Twitter: Target of a Not-so-Normal DDoS Attack? http://blog.trendmicro.com/?p=18695</description>
		<content:encoded><![CDATA[<p>Twitter: Target of a Not-so-Normal DDoS Attack? <a href="http://blog.trendmicro.com/?p=18695" rel="nofollow">http://blog.trendmicro.com/?p=18695</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bubbles</title>
		<link>http://blog.trendmicro.com/twitter-target-of-a-not-so-normal-ddos-attack/comment-page-1/#comment-31583</link>
		<dc:creator>Bubbles</dc:creator>
		<pubDate>Tue, 11 Aug 2009 12:28:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.trendmicro.com/?p=18695#comment-31583</guid>
		<description>The experts are offbase as usual.   The attacks against Cyxymu were routed through compromised web hosting servers and compromised personal computers.  The command and control targeted Cyxymu and the zombied personal PC&#039;s and compromised web hosting servers all started making request against Cyxymu&#039;s web pages.

How in the h*ll are these botnets ever going to get dismantled when the experts are so far off in left field with their guesses and speculations.  

Let the experts have the IP&#039;s of the traffic that targeted Cyxymu&#039;s web pages.  Run those IPs against a whois and see how many lead to web hosting providers ( where compromised web sites will be found ) - and see how many lead to compromised high speed internet users ( where the Internet Service Providers are completely asleep regarding the malicious traffic being poured out of compromised personal computers of end users ).

Come on people.  Figure it out.  I am tired of hearing misdiagnosis of the origins of these attacks.  And we need to start dismantling these botnets by force, if necessary, if incompetent hosting providers are unable to monitor anomalies in the outbound traffic originating from web sites or web servers within their company&#039;s allocated IP ranges.</description>
		<content:encoded><![CDATA[<p>The experts are offbase as usual.   The attacks against Cyxymu were routed through compromised web hosting servers and compromised personal computers.  The command and control targeted Cyxymu and the zombied personal PC&#8217;s and compromised web hosting servers all started making request against Cyxymu&#8217;s web pages.</p>
<p>How in the h*ll are these botnets ever going to get dismantled when the experts are so far off in left field with their guesses and speculations.  </p>
<p>Let the experts have the IP&#8217;s of the traffic that targeted Cyxymu&#8217;s web pages.  Run those IPs against a whois and see how many lead to web hosting providers ( where compromised web sites will be found ) &#8211; and see how many lead to compromised high speed internet users ( where the Internet Service Providers are completely asleep regarding the malicious traffic being poured out of compromised personal computers of end users ).</p>
<p>Come on people.  Figure it out.  I am tired of hearing misdiagnosis of the origins of these attacks.  And we need to start dismantling these botnets by force, if necessary, if incompetent hosting providers are unable to monitor anomalies in the outbound traffic originating from web sites or web servers within their company&#8217;s allocated IP ranges.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

