<?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: Kneber Update</title>
	<atom:link href="http://www.networkforensics.com/2010/02/19/kneber-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.networkforensics.com/2010/02/19/kneber-update/</link>
	<description></description>
	<lastBuildDate>Fri, 20 Aug 2010 15:21:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Zeus Botnet: Interesting and In-depth Articles &#171; Mister Reiner</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-112</link>
		<dc:creator>Zeus Botnet: Interesting and In-depth Articles &#171; Mister Reiner</dc:creator>
		<pubDate>Sat, 05 Jun 2010 10:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-112</guid>
		<description>[...] NetWitness Blog: Kneber Update (Web page &#8211; An attempt to set the record straight) [...]</description>
		<content:encoded><![CDATA[<p>[...] NetWitness Blog: Kneber Update (Web page &#8211; An attempt to set the record straight) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-67</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Tue, 23 Feb 2010 10:35:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-67</guid>
		<description>Where possible, and within reason, we have notified responsible network owners of the IP addresses that are infected.  In many articles, it mentioned we are working to notify parties.  We continue to work with others including service providers, banks, and social networking sites.</description>
		<content:encoded><![CDATA[<p>Where possible, and within reason, we have notified responsible network owners of the IP addresses that are infected.  In many articles, it mentioned we are working to notify parties.  We continue to work with others including service providers, banks, and social networking sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-66</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Tue, 23 Feb 2010 10:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-66</guid>
		<description>In order:

The McAfee Rootkit Detector, when we tested it the other day, did not detect this &quot;variant.&quot;  We say variant, because these adversaries can take the executable and repackage it with various tools that make it undetectable to many signature based solutions.  Since the posting of this, we have various additional repackaged versions that remain undetected.

All AV vendors have similar challenges detecting these repackaged versions.  If your signatures are up to date, you will likely detect the original variant.  However, there are more that have been released that are difficult to detect.  AV plays an important role here - but cannot be relied upon exclusively.

The IE vulnerability can be used to deliver malware.  This particular group has access to a very large spamming bot, and is using custom crafted emails that can be very convincing.

See last response on patching.  If they successfully convince you to open an trojan document, or use a zero day, or to voluntarily install, you will be infected.  Patching, like AV, is part of the solution and makes you more resistant, but does not make anyone immune.</description>
		<content:encoded><![CDATA[<p>In order:</p>
<p>The McAfee Rootkit Detector, when we tested it the other day, did not detect this &#8220;variant.&#8221;  We say variant, because these adversaries can take the executable and repackage it with various tools that make it undetectable to many signature based solutions.  Since the posting of this, we have various additional repackaged versions that remain undetected.</p>
<p>All AV vendors have similar challenges detecting these repackaged versions.  If your signatures are up to date, you will likely detect the original variant.  However, there are more that have been released that are difficult to detect.  AV plays an important role here &#8211; but cannot be relied upon exclusively.</p>
<p>The IE vulnerability can be used to deliver malware.  This particular group has access to a very large spamming bot, and is using custom crafted emails that can be very convincing.</p>
<p>See last response on patching.  If they successfully convince you to open an trojan document, or use a zero day, or to voluntarily install, you will be infected.  Patching, like AV, is part of the solution and makes you more resistant, but does not make anyone immune.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EJ</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-64</link>
		<dc:creator>EJ</dc:creator>
		<pubDate>Mon, 22 Feb 2010 17:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-64</guid>
		<description>One item of interest to me in this but I haven&#039;t seen commented on is whether the victims that were detected in this 74K node botnet have been notified of their participation?</description>
		<content:encoded><![CDATA[<p>One item of interest to me in this but I haven&#8217;t seen commented on is whether the victims that were detected in this 74K node botnet have been notified of their participation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yaggi</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-62</link>
		<dc:creator>Yaggi</dc:creator>
		<pubDate>Mon, 22 Feb 2010 01:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-62</guid>
		<description>Hi 

Currently, we see many machines infected Zeus (74.118.192.124 via tcp 5900), we are advised to use McAfee Rootkit Detector.

We are using Symantec so we just make sure that our definitions is updated and run a full scan (safe mode) http://securityresponse.symantec.com/security_response/writeup.jsp?docid=2010-011016-3514-99  or we really need to use this mcafee rootkit detective?

BY the way, about infection, is it exploiting something in a unpatch vulnerabilities in the IE browser?
I wanted to know if this issue similar to conficker that as long as we patch MS08-067 the machine is conficker free?

Or this malware can infect users even if they have no vulnerability at all as long as the user will click malicious something on the net?
how can a certain malware infect a fully patch machine (assuming no more 0-day vulnerability issue), can it still infect or exploit?

Thanks</description>
		<content:encoded><![CDATA[<p>Hi </p>
<p>Currently, we see many machines infected Zeus (74.118.192.124 via tcp 5900), we are advised to use McAfee Rootkit Detector.</p>
<p>We are using Symantec so we just make sure that our definitions is updated and run a full scan (safe mode) <a href="http://securityresponse.symantec.com/security_response/writeup.jsp?docid=2010-011016-3514-99" rel="nofollow">http://securityresponse.symantec.com/security_response/writeup.jsp?docid=2010-011016-3514-99</a>  or we really need to use this mcafee rootkit detective?</p>
<p>BY the way, about infection, is it exploiting something in a unpatch vulnerabilities in the IE browser?<br />
I wanted to know if this issue similar to conficker that as long as we patch MS08-067 the machine is conficker free?</p>
<p>Or this malware can infect users even if they have no vulnerability at all as long as the user will click malicious something on the net?<br />
how can a certain malware infect a fully patch machine (assuming no more 0-day vulnerability issue), can it still infect or exploit?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-59</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Sun, 21 Feb 2010 15:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-59</guid>
		<description>This is not an easy question to answer.  While Anti-Virus and Anti-Malware technologies are indeed important, it is simply too easy to repackage these exploits to bypass technologies that are primarily signature based.  There is a network equivalent there in IDS/IPS technologies as well.  It takes days, weeks, months for some of these protection technologies to get updated.  You have to expect that compromise is inevitable, and put in place technologies that are capable of &quot;filling the gaps&quot; left by the others.  At NW, we deliver visibility and understanding to all network activity, and detection of this particular type of activity is fairly commonplace.  Of course the adversary is getting ever more advanced.  You need the ability to look back over time once you DO know characteristics of the attack and assess the damage / develop a remediation plan.  Without that network memory, you will have no insight into the amount or type of data stolen.  There is no magic pill.  There is no &quot;secure.&quot;</description>
		<content:encoded><![CDATA[<p>This is not an easy question to answer.  While Anti-Virus and Anti-Malware technologies are indeed important, it is simply too easy to repackage these exploits to bypass technologies that are primarily signature based.  There is a network equivalent there in IDS/IPS technologies as well.  It takes days, weeks, months for some of these protection technologies to get updated.  You have to expect that compromise is inevitable, and put in place technologies that are capable of &#8220;filling the gaps&#8221; left by the others.  At NW, we deliver visibility and understanding to all network activity, and detection of this particular type of activity is fairly commonplace.  Of course the adversary is getting ever more advanced.  You need the ability to look back over time once you DO know characteristics of the attack and assess the damage / develop a remediation plan.  Without that network memory, you will have no insight into the amount or type of data stolen.  There is no magic pill.  There is no &#8220;secure.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Comwise Internetwork Sdn Bhd &#187; Blog Archive &#187; Why it is all too easy to become a cybercriminal</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-57</link>
		<dc:creator>Comwise Internetwork Sdn Bhd &#187; Blog Archive &#187; Why it is all too easy to become a cybercriminal</dc:creator>
		<pubDate>Sat, 20 Feb 2010 15:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-57</guid>
		<description>[...] NetWitness’ media coup  sparked some sniping from rival tech security vendors McAfee and Symantec; each cast aspersions on NetWitness’ characterizations of the significance of its findings. NetWitness shot back with this point-by-point response. [...]</description>
		<content:encoded><![CDATA[<p>[...] NetWitness’ media coup  sparked some sniping from rival tech security vendors McAfee and Symantec; each cast aspersions on NetWitness’ characterizations of the significance of its findings. NetWitness shot back with this point-by-point response. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.networkforensics.com/2010/02/19/kneber-update/comment-page-1/#comment-53</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 19 Feb 2010 21:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkforensics.com/?p=207#comment-53</guid>
		<description>So what can the average user do to fix/mitigate this botnet or any for that matter?</description>
		<content:encoded><![CDATA[<p>So what can the average user do to fix/mitigate this botnet or any for that matter?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
