<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
<channel>
    <title>honeyblog - malware</title>
    <link>http://honeyblog.org/</link>
    <description>A blog on honeypots, honeynets, and more...</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3.1-1 - http://www.s9y.org/</generator>
    <managingEditor>thorsten.holz@gmail.com</managingEditor>
<pubDate>Tue, 02 Mar 2010 21:29:00 GMT</pubDate>

    <image>
        <url>http://honeyblog.org/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: honeyblog - malware - A blog on honeypots, honeynets, and more...</title>
        <link>http://honeyblog.org/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Waledac Infection Check</title>
    <link>http://honeyblog.org/archives/53-Waledac-Infection-Check.html</link>
            <category>admin</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/53-Waledac-Infection-Check.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=53</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=53</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/twitter.com/sqrtsben&#039;);&quot;  href=&quot;http://twitter.com/sqrtsben&quot;&gt;Ben Stock&lt;/a&gt; has implemented a web service to check a given IP address for infection with Waledac, similar to the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.confickerworkinggroup.org/infection_test/cfeyechart.html&#039;);&quot;  href=&quot;http://www.confickerworkinggroup.org/infection_test/cfeyechart.html&quot;&gt;Conficker Eye Chart&lt;/a&gt;. The idea is that we are currently tracking Waledac as part of the take-down effort and thus we have a pretty good overview of the individual bots within the botnet. Therefore we are in a position to determine if we have seen a given IP address in the recent past as a bot, which indicates that this IP address might be related to a Waledac infection. Of course, effects like NAT or DHCP need to be taken into account: if an IP address is not listed, this does not necessarily mean that you are not infected. &lt;br /&gt;
&lt;br /&gt;
The check is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/mwanalysis.org/waledac/&#039;);&quot;  href=&quot;http://mwanalysis.org/waledac/&quot;&gt;http://mwanalysis.org/waledac/&lt;/a&gt;, feedback is welcome!&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 02 Mar 2010 22:29:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/53-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Waledac Takedown Successful</title>
    <link>http://honeyblog.org/archives/52-Waledac-Takedown-Successful.html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/52-Waledac-Takedown-Successful.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=52</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=52</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    A few weeks ago, I blogged about our paper &quot;&lt;a href=&quot;http://honeyblog.org/archives/44-Walowdac-Analysis-of-a-Peer-to-Peer-Botnet.html&quot;&gt;Walowdac – Analysis of a Peer-to-Peer Botnet&lt;/a&gt;&quot;. The paper provides an overview of the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?Name=Trojan%3aWin32%2fWaledac&#039;);&quot;  href=&quot;http://www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?Name=Trojan%3aWin32%2fWaledac&quot;&gt;Waledac&lt;/a&gt; &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/us.trendmicro.com/imperia/md/content/us/pdf/threats/securitylibrary/infiltrating_the_waledac_botnet_v2.pdf&#039;);&quot;  href=&quot;http://us.trendmicro.com/imperia/md/content/us/pdf/threats/securitylibrary/infiltrating_the_waledac_botnet_v2.pdf&quot;&gt;botnet&lt;/a&gt; and its specific aspects compared to Storm Worm and similar peer-to-peer botnets. The paper also contains some measurement results for the botnet like the typical number of online bots and similar statistics.&lt;br /&gt;
&lt;br /&gt;
In the last couple of days, the situation changed a bit: we worked on an active takedown of the botnet together with experts from Microsoft, Shadowserver, the University of Mannheim, University of Bonn, University of Washington, Symantec and others. The operation is know within Microsoft as &quot;Operation b49&quot; and involved domain takedowns and additional technical countermeasures. Microsoft also did some fantastic work on the legal side, the complaint filed by Microsoft (&quot;&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.microsoft.com/presspass/events/rsa/docs/Complaint.pdf&#039;);&quot;  href=&quot;http://www.microsoft.com/presspass/events/rsa/docs/Complaint.pdf&quot;&gt;Microsoft Corporation v. John Does 1-27, et. al.&lt;/a&gt;&quot;) is available online. As a result, the communication infrastructure of Waledac has been disrupted to a certain extent and the botmaster can effectively not send commands to the bots. The &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.sudosecure.net/waledac/index.php&#039;);&quot;  href=&quot;http://www.sudosecure.net/waledac/index.php&quot;&gt;Waledac Tracker&lt;/a&gt; by  &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.sudosecure.net/&#039;);&quot;  href=&quot;http://www.sudosecure.net/&quot;&gt;sudosecure.net&lt;/a&gt; also shows a nice decline in the number of bots for the last few days. Note, however, that the infected machines are still up and running, thus some clean-up at that side is still necessary...&lt;br /&gt;
&lt;br /&gt;
You can read more about the story in a blog post by Microsoft: &quot;&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/microsoftontheissues.com/cs/blogs/mscorp/archive/2010/02/24/cracking-down-on-botnets.aspx&#039;);&quot;  href=&quot;http://microsoftontheissues.com/cs/blogs/mscorp/archive/2010/02/24/cracking-down-on-botnets.aspx&quot;&gt;Cracking Down on Botnets&lt;/a&gt;&quot;. And I will update the blog with new information once we start to analyze the collected data...&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 25 Feb 2010 15:57:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/52-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Data Set For Malware Clustering/Classification</title>
    <link>http://honeyblog.org/archives/50-Data-Set-For-Malware-ClusteringClassification.html</link>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/50-Data-Set-For-Malware-ClusteringClassification.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=50</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=50</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    About one month ago I blogged about our research on &lt;a href=&quot;http://honeyblog.org/archives/42-Automatic-Analysis-of-Malware-Behavior-using-Machine-Learning.html&quot;&gt;malware clustering and classification&lt;/a&gt;. We have now also released the full data set from our experiments, such that other people can reproduce the results and compare our approach to theirs. You can find all information at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/pi1.informatik.uni-mannheim.de/malheur/&#039;);&quot;  href=&quot;http://pi1.informatik.uni-mannheim.de/malheur/&quot;&gt;http://pi1.informatik.uni-mannheim.de/malheur/&lt;/a&gt;, together with a description of the different data.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Quick overview of the data&lt;/em&gt;:&lt;br /&gt;
&lt;blockquote&gt;Our reference data set is extracted from our large database of malware binaries maintained at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cwsandbox.org&#039;);&quot;  href=&quot;http://cwsandbox.org&quot;&gt;CWSandbox&lt;/a&gt;. The malware binaries have been collected over a period of three years from a variety of sources. From the overall database, we select binaries which have been assigned to a known class of malware by the majority of six independent anti-virus products. We append the overall anti-virus label to the filename of each report. Although anti-virus labels suffer from inconsistency, we expect the selection using different scanners to be reasonable consistent and accurate. To compensate for the skewed distribution of classes, we discard classes with less than 20 samples and restrict the maximum contribution of each class to 300 binaries. The selected malware binaries are then executed and monitored using CWSandbox, resulting in a total of 3.133 behavior reports in MIST format. &lt;br /&gt;
&lt;br /&gt;
The application data set consists of seven chunks of malware binaries obtained from the anti-malware vendor Sunbelt Software. The binaries correspond to malware collected during seven consecutive days in August 2009 and originate from a variety of sources. Sunbelt Software uses these very samples to create and update signatures for their VIPRE anti-malware product as well as for their security data feed ThreatTrack. The complete test data set consists of 33.698 behavior reports in MIST format. &lt;/blockquote&gt;&lt;br /&gt;
The full technical report is available at &lt;a href=&quot;http://honeyblog.org/junkyard/paper/malheur-TR-2009.pdf&quot;&gt;http://honeyblog.org/junkyard/paper/malheur-TR-2009.pdf&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Update&lt;/em&gt;: I changed the terms within the description to use the correct description.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 29 Jan 2010 14:08:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/50-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Call for Papers: LEET'10</title>
    <link>http://honeyblog.org/archives/49-Call-for-Papers-LEET10.html</link>
            <category>admin</category>
            <category>honeynets</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/49-Call-for-Papers-LEET10.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=49</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=49</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The submissions deadline for the 3rd USENIX Workshop on Large-Scale Exploits and Emergent Threats (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/events/leet10/&#039;);&quot;  href=&quot;http://www.usenix.org/events/leet10/&quot;&gt;LEET &#039;10&lt;/a&gt;) is quickly approaching. Please submit your work by Thursday, February 25, 2010, 11:59 p.m. PST. The full call for papers is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/events/leet10/cfp/&#039;);&quot;  href=&quot;http://www.usenix.org/events/leet10/cfp/&quot;&gt;http://www.usenix.org/events/leet10/cfp/&lt;/a&gt;, see an overview below:&lt;br /&gt;
&lt;blockquote&gt;&lt;b&gt;Topics&lt;/b&gt;&lt;br /&gt;
Now in its third year, LEET continues to provide a unique forum for the discussion of threats to the confidentiality of our data, the integrity of digital transactions, and the dependability of the technologies we increasingly rely on. We encourage submissions of papers that focus on the malicious activities themselves (e.g., reconnaissance, exploitation, privilege escalation, rootkit installation, attack), our responses as defenders (e.g., prevention, detection, and mitigation), or the social, political, and economic goals driving these malicious activities and the legal and ethical codes guiding our defensive responses.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Overview&lt;/b&gt;&lt;br /&gt;
Information technology (IT) adds $2 trillion annually to the US economy alone. While these technologies have enabled significant global economic growth, they have become rich targets for malicious activity. The US Federal Bureau of Investigation (FBI) indicated that cyber crime reached an all-time high in 2008; cyber crime now ranks as the FBI&#039;s third highest priority, behind such dramatic threats as counter-terrorism and counter-espionage. Much of this malicious activity is driven by economic incentives, but recently we have seen the emergence of highly visible, politically motivated attacks. While the motivations for malicious behavior and the technical mechanisms that enable them remain rich areas of research, it is clear that today our global society is faced with a wide range of cyber criminal activities: spam, phishing, denial of service, click fraud, etc.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Workshop Format&lt;/b&gt;&lt;br /&gt;
LEET aims to be a true workshop, with the twin goals of fostering the development of preliminary work and helping to unify the broad community of researchers and practitioners who focus on worms, bots, spam, spyware, phishing, DDoS, and the ever-increasing palette of large-scale Internet-based threats. Intriguing preliminary results and thought-provoking ideas will be strongly favored; papers will be selected for their potential to stimulate discussion in the workshop. Each author will have 15 minutes to present his or her work, followed by 15 minutes of discussion with the workshop participants.&lt;/blockquote&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 25 Jan 2010 09:03:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/49-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>&quot;Studying Aspects of the Underground Economy&quot;</title>
    <link>http://honeyblog.org/archives/48-Studying-Aspects-of-the-Underground-Economy.html</link>
            <category>honeynets</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/48-Studying-Aspects-of-the-Underground-Economy.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=48</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=48</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Today I gave a  &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.icsi.berkeley.edu/cgi-bin/events/event.pl?ID=000563&#039;);&quot;  href=&quot;http://www.icsi.berkeley.edu/cgi-bin/events/event.pl?ID=000563&quot;&gt;talk&lt;/a&gt; at the International Computer Science Institute (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.icsi.berkeley.edu/about/index.html&#039;);&quot;  href=&quot;http://www.icsi.berkeley.edu/about/index.html&quot;&gt;ICSI&lt;/a&gt;) that focussed on some of the research I did in the past year. The slides are now &lt;a href=&quot;http://honeyblog.org/junkyard/presentations/10_underground-economy_ICSI.pdf&quot;&gt;available&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
With the growing digital economy, it comes as no surprise that criminal activities in digital business have lead to a digital underground economy. Because it is such a fast-moving field, tracking and understanding this underground economy is difficult and most information in this area is vague. In this talk, we discuss several approaches to study the structure of these underground markets. In particular, we present a method with which it is possible to directly analyze the amount of data harvested through keylogger-based attacks in a highly automated fashion. Based on real-world data, we can get a glimpse into the digital underground economy. However, many open questions remain that will be discussed in the last part of the talk.&lt;br /&gt;
&lt;br /&gt;
You can get the slides at &lt;a href=&quot;http://honeyblog.org/junkyard/presentations/10_underground-economy_ICSI.pdf&quot;&gt;http:///honeyblog.org/junkyard/presentations/10_underground-economy_ICSI.pdf&lt;/a&gt;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Wed, 20 Jan 2010 06:53:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/48-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Challenge 1 posted - Signed books as prizes!</title>
    <link>http://honeyblog.org/archives/46-Challenge-1-posted-Signed-books-as-prizes!.html</link>
            <category>honeynets</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/46-Challenge-1-posted-Signed-books-as-prizes!.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=46</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=46</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The first challenge of the Honeynet Forensic Challenge 2010 has been posted at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/honeynet.org/node/504&#039;);&quot;  href=&quot;http://honeynet.org/node/504&quot;&gt;http://honeynet.org/node/504&lt;/a&gt;. The task is to analyze a packet capture that was collected by a honeypot. Analyze and answer the following questions:&lt;br /&gt;
&lt;ol&gt;&lt;li&gt;Which systems (i.e. IP addresses) are involved? (2pts)&lt;/li&gt;&lt;li&gt;What can you find out about the attacking host (e.g., where is it located)? (2pts) &lt;/li&gt;&lt;li&gt;How many TCP sessions are contained in the dump file? (2pts)&lt;/li&gt;&lt;li&gt;How long did it take to perform the attack? (2pts)&lt;/li&gt;&lt;li&gt;Which operating system was targeted by the attack? And which service? Which vulnerability? (6pts) &lt;/li&gt;&lt;li&gt;Can you sketch an overview of the general actions performed by the attacker? (6pts) &lt;/li&gt;&lt;li&gt;What specific vulnerability was attacked? (2pts) &lt;/li&gt;&lt;li&gt;What actions does the shellcode perform? Pls list the shellcode. (8pts) &lt;/li&gt;&lt;li&gt;Do you think a Honeypot was used to pose as a vulnerable victim? Why? (6pts) &lt;/li&gt;&lt;li&gt;Was there malware involved? Whats the name of the malware? (We are not looking for a detailed malware analysis for this challenge) (2pts) &lt;/li&gt;&lt;li&gt;Do you think this is a manual or an automated attack? Why? (2pts) &lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;
Get the pcap at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/honeynet.org/files/attack-trace.pcap_.gz&#039;);&quot;  href=&quot;http://honeynet.org/files/attack-trace.pcap_.gz&quot;&gt;http://honeynet.org/files/attack-trace.pcap_.gz&lt;/a&gt;, they were provided together with the questions by Tillmann Werner. Deadline for submissions is Monday, February 1st 2010 at 17:00 EST. There will be some small prizes, among them signed copies of our book &quot;&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.amazon.com/gp/product/0321336321?ie=UTF8&amp;amp;amp;tag=honeyblogorg-20&amp;amp;amp;linkCode=as2&amp;amp;amp;camp=1789&amp;amp;amp;creative=9325&amp;amp;amp;creativeASIN=0321336321&#039;);&quot;  href=&quot;http://www.amazon.com/gp/product/0321336321?ie=UTF8&amp;amp;tag=honeyblogorg-20&amp;amp;linkCode=as2&amp;amp;camp=1789&amp;amp;creative=9325&amp;amp;creativeASIN=0321336321&quot;&gt;Virtual Honeypots: From Botnet Tracking to Intrusion Detection&lt;/a&gt;&quot;. Full information is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/honeynet.org/node/504&#039;);&quot;  href=&quot;http://honeynet.org/node/504&quot;&gt;http://honeynet.org/node/504&lt;/a&gt;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 18 Jan 2010 08:56:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/46-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Walowdac – Analysis of a Peer-to-Peer Botnet</title>
    <link>http://honeyblog.org/archives/44-Walowdac-Analysis-of-a-Peer-to-Peer-Botnet.html</link>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/44-Walowdac-Analysis-of-a-Peer-to-Peer-Botnet.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=44</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=44</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    &lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/waledac-wc.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/waledac-wc.png&#039;,&#039;Zoom&#039;,&#039;height=554,width=822,top=180.5,left=316.5,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:29 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;73&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/waledac-wc.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; One of the most interesting botnets of 2009 was Waledac: the botnet implements a peer-to-peer-based communication channel and it can be seen as the successor of Storm Worm, since it implemented many similar ideas (e.g., a very similar language for spam templates was used). The researchers from Trend Micro had published an &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/us.trendmicro.com/imperia/md/content/us/pdf/threats/securitylibrary/infiltrating_the_waledac_botnet_v2.pdf&#039;);&quot;  href=&quot;http://us.trendmicro.com/imperia/md/content/us/pdf/threats/securitylibrary/infiltrating_the_waledac_botnet_v2.pdf&quot;&gt;analysis&lt;/a&gt; of the botnet and we also examined the botnet. The result is a paper entitled &quot;&lt;a href=&quot;http://honeyblog.org/junkyard/paper/waledac-ec2nd09.pdf&quot;&gt;Walowdac - Analysis of a Peer-to-Peer Botnet&lt;/a&gt;&quot;: instead of passively observing the network, we implemented an active infiltration component. We emulate the protocol of a bot and are able to observe the inner communication aspects of the network. As a result, we obtain an in-depth overview of the botnet that enables us to study different aspects of the network, e.g., efficiency of the spam campaigns or number of active bots. As a small peak of the results, the following pictures shows the number of active bots in different countries on a specific day in August 2009. We can for example observe diurnal patterns and clearly see the effects of timezones on the size of the botnet:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/unique_20090824.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/unique_20090824.png&#039;,&#039;Zoom&#039;,&#039;height=1101,width=1989,top=-93,left=-267,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:30 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;61&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/unique_20090824.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
A botnet is a network of compromised machines under the control of an attacker. Botnets are the driving force behind several misuses on the Internet, for example spam mails or automated identity theft. In this paper, we study the most prevalent peer-to-peer botnet in 2009: &lt;em&gt;Waledac&lt;/em&gt;. We present our infiltration of the Waledac botnet, which can be seen as the successor of the Storm Worm botnet. To achieve this we implemented a clone of the Waledac bot named &lt;em&gt;Walowdac&lt;/em&gt;. It implements the communication features of Waledac but does not cause any harm, i.e., no spam emails are sent and no other commands are executed. With the help of this tool we observed a minimum daily population of 55,000 Waledac bots and a total of roughly 390,000 infected machines throughout the world. Furthermore, we gathered internal information about the success rates of spam campaigns and newly introduced features like the theft of credentials from victim machines.&lt;br /&gt;
&lt;br /&gt;
The paper was joint work with Ben Stock, Jan Göbel, Markus Engelberth, and Felix C. Freiling. The full paper is available at &lt;a href=&quot;http://honeyblog.org/junkyard/paper/waledac-ec2nd09.pdf&quot;&gt;http://honeyblog.org/junkyard/paper/waledac-ec2nd09.pdf&lt;/a&gt; and it was published at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/2009.ec2nd.org/&#039;);&quot;  href=&quot;http://2009.ec2nd.org/&quot;&gt;EC2ND 2009&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Sun, 03 Jan 2010 12:26:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/44-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Automatic Analysis of Malware Behavior using Machine Learning</title>
    <link>http://honeyblog.org/archives/42-Automatic-Analysis-of-Malware-Behavior-using-Machine-Learning.html</link>
            <category>CWSandbox</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/42-Automatic-Analysis-of-Malware-Behavior-using-Machine-Learning.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=42</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=42</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    In the last couple of years, several honeypot solutions to automatically &quot;collect&quot; malware samples were developed. With these tools, it is possible to obtain copies of malware samples without any human interaction. As a result, we are able to collect quite a few malware samples per day, which then also need to be analyzed. Thus, several sandbox solutions were developed that automate the analysis step by performing dynamic, behavior-based analysis. The result of the dynamic analysis is typically a report that summarizes the observed behavior. The next logical step is to use that information to perform malware classification and malware clustering: at the end of that process, we can then obtain information about which samples perform basically the same kind of activity. We can then automatically find variants of well-known threats, identify new malware families, and reduce the manual effort needed to analyze the large number of incoming malware samples.&lt;br /&gt;
&lt;br /&gt;
&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/malware-clustering-wc.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:27 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;57&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/malware-clustering-wc.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; In the last couple of months, we worked on malware classification and malware clustering. The results are summarized in a &lt;a href=&quot;http://honeyblog.org/junkyard/paper/malheur-TR-2009.pdf&quot;&gt;technical report&lt;/a&gt;. In the article, we introduce a learning-based framework for automatic analysis of malware behavior. To apply this framework in practice, it suffices to collect a large number of malware samples and monitor their behavior using a sandbox environment. By embedding the observed behavior in a vector space, reflecting behavioral patterns in its dimensions, we are able to apply learning algorithms, such as clustering and classification, for analysis of malware behavior. Both techniques are important for an automated processing of malware samples and we show in several experiments that our techniques significantly improve previous work in this area. For example, the concept of prototypes allows for efficient clustering and classification, while also enabling a security researcher to focus manual analysis on prototypes instead of all malware samples. Moreover, we introduce a technique to perform behavior-based analysis in an incremental way that avoids run-time and memory overhead inherent to previous approaches.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;&lt;br /&gt;
Malicious software — so called &lt;em&gt;malware&lt;/em&gt; — poses a major threat to the security of computer systems. The amount and diversity of its variants render classic security defenses ineffective, such that millions of hosts in the Internet are infected with malware in form of computer viruses, Internet worms and Trojan horses. While obfuscation and polymorphism employed by malware largely impede detection at file level, the dynamic analysis of malware binaries during run-time provides an instrument for characterizing and defending against the threat of malicious software.&lt;br /&gt;
In this article, we propose a framework for automatic analysis of malware behavior using machine learning. The framework allows for automatically identifying novel classes of malware with similar behavior (&lt;em&gt;clustering&lt;/em&gt;) and assigning unknown malware to these discovered classes (&lt;em&gt;classification&lt;/em&gt;). Based on both, clustering and classification, we propose an incremental approach for behavior-based analysis, capable to process the behavior of thousands of malware binaries on a daily basis. The incremental analysis significantly reduces the run-time overhead of current analysis methods, while providing an accurate discovery and discrimination of novel malware variants.&lt;br /&gt;
&lt;br /&gt;
The full technical report is available at &lt;a href=&quot;http://honeyblog.org/junkyard/paper/malheur-TR-2009.pdf&quot;&gt;http://honeyblog.org/junkyard/paper/malheur-TR-2009.pd&lt;/a&gt;. It was joint work with &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/blog.mlsec.org/&#039;);&quot;  href=&quot;http://blog.mlsec.org/&quot;&gt;Konrad Rieck&lt;/a&gt;, &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.omnivora.de/&#039;);&quot;  href=&quot;http://www.omnivora.de/&quot;&gt;Philipp Trinius&lt;/a&gt;, and &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cwse.de/&#039;);&quot;  href=&quot;http://cwse.de/&quot;&gt;Carsten Willems&lt;/a&gt;. And the word cloud was generated using &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.wordle.net/&#039;);&quot;  href=&quot;http://www.wordle.net/&quot;&gt;http://www.wordle.net/&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 28 Dec 2009 12:15:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/42-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>AV Tracker</title>
    <link>http://honeyblog.org/archives/37-AV-Tracker.html</link>
            <category>CWSandbox</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/37-AV-Tracker.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=37</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=37</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    A couple of days ago, the website &quot;AV Tracker&quot; went online, which publishes information about various automated analysis systems. The idea is that the attacker uploads a binary to an analysis system, waits for the sample to be executed, and then the binary phones home some information to a server under the control of the attacker. The collected information is then published at &quot;AV Tracker&quot;, exposing information about the analysis systems. Besides some well-known AV companies, also &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cwsandbox.org&#039;);&quot;  href=&quot;http://cwsandbox.org&quot;&gt;CWSandbox&lt;/a&gt; and &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/anubis.iseclab.org&#039;);&quot;  href=&quot;http://anubis.iseclab.org&quot;&gt;Anubis&lt;/a&gt; were affected. &lt;br /&gt;
&lt;br /&gt;
We analyzed the binary and found that it sends a simply HTTP request, in which all extracted information is encoded. An example for an analysis report generated by one of the samples is &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/anubis.iseclab.org/?action=result&amp;amp;amp;task_id=361b5a8ee7235954252b02d33b3a7d24&#039;);&quot;  href=&quot;http://anubis.iseclab.org/?action=result&amp;amp;task_id=361b5a8ee7235954252b02d33b3a7d24&quot;&gt;http://anubis.iseclab.org/?action=result&amp;task_id=361b5a8ee7235954252b02d33b3a7d24&lt;/a&gt;. This can be defeated by blocking access to the reporting server or by regularly changing the IP address of the analysis systems, but at the end this will be some kind of arms race again.&lt;br /&gt;
&lt;br /&gt;
Some other interesting information is also embedded in the binary. When extracting the strings from the sample, the following text becomes visible (some information is hidden by dots):&lt;br /&gt;
&lt;blockquote&gt;This is Peter Kl....... fuck ...... fuck the world fuck you all!&lt;br /&gt;
I was once working with ...... and was a white hat, now I am the worst mean motherfucker black hat and I am selling the source code of ...... .. :D&lt;br /&gt;
I am with the &lt;s&gt;Sinowal&lt;/s&gt;Whistler developers, funny days, aren&#039;t ;) and fuck ..... they don&#039;t have no idea :D bitches&lt;/blockquote&gt;&lt;br /&gt;
A related article was also published today at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.viruslist.com/en/weblog?weblogid=208187881&#039;);&quot;  href=&quot;http://www.viruslist.com/en/weblog?weblogid=208187881&quot;&gt;http://www.viruslist.com/en/weblog&lt;/a&gt; under the title &quot;A black hat loses control&quot;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 22 Oct 2009 12:49:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/37-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>$645.00 ...</title>
    <link>http://honeyblog.org/archives/36-645.00-....html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/36-645.00-....html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=36</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=36</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    ... is the amount I am worth in the underground economy, at least according to Symantec&#039;s new &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/everyclickmatters.com/&#039;);&quot;  href=&quot;http://everyclickmatters.com/&quot;&gt;website&lt;/a&gt; on which they advertise (in a somewhat entertaining way) Norton 2010 products. Here are the results when I take the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/everyclickmatters.com/victim/assessment.html&#039;);&quot;  href=&quot;http://everyclickmatters.com/victim/assessment.html&quot;&gt;risk assessment&lt;/a&gt;:&lt;br /&gt;
&lt;blockquote&gt;[...] In the underground economy, you&#039;re really worth about $645.00. And that&#039;s on a good day.&lt;br /&gt;
Your entire digital life could go on the auction block for as little as $10.96, whether you like it or not.&lt;/blockquote&gt;&lt;br /&gt;
How they compute these numbers and on what methodology / measurements this is based remains completely unclear, after all it is just some kind of marketing. But the movies are funny, perhaps they can serve as some kind of security awareness campaign. Main drawback is that the website is almost completely built on top of Flash and JavaScript - how about not using all these techniques next time? In some recent measurements we found that the vast majority of web surfers still have an unpatched version of Flash installed, better teach them to regularly update their system next time...&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 10 Sep 2009 23:27:13 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/36-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Thread Graphs for Visualizing Malware Behavior</title>
    <link>http://honeyblog.org/archives/34-Thread-Graphs-for-Visualizing-Malware-Behavior.html</link>
            <category>CWSandbox</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/34-Thread-Graphs-for-Visualizing-Malware-Behavior.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=34</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=34</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The &lt;a href=&quot;http://honeyblog.org/archives/33-Visual-Analysis-of-Malware-Behavior-Using-Treemaps-and-Thread-Graphs.html&quot;&gt;last blog post&lt;/a&gt; dealt with our recent research on visualizing malware behavior. Now a quick update on the &lt;em&gt;thread graphs&lt;/em&gt; we generate for visualizing malware behavior: since tree maps display nothing about the sequence of operations, we use another presentation format to visualize the temporal behavior of the individual threads of a sample. A thread graph can be regarded as a behavioral ﬁngerprint of the sample that represents the temporal order of executed system commands and the different threads spawned by a binary. The x-axis represents the time (sequence of performed actions), while the y-axis indicates the operation/section of the performed action. An analyst can then study this behavior graph to quickly learn more about the actions of each individual thread.&lt;br /&gt;
&lt;br /&gt;
The following two pictures show examples of this kind of visualization:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/adultbrowser-tg.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/adultbrowser-tg.png&#039;,&#039;Zoom&#039;,&#039;height=1017,width=1612,top=-51,left=-78.5,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:25 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;69&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/adultbrowser-tg.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/hookshell-tg.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/hookshell-tg.png&#039;,&#039;Zoom&#039;,&#039;height=1017,width=1612,top=-51,left=-78.5,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:24 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;69&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/hookshell-tg.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
On the left hand picture, we can see that one thread is responsible for the majority of operations for the sample. This thread performs many registry operations and initially performs many network- and system-related operations (operations 90-140). Additionally, two more threads are spawned, but they perform only a limited amount of operations during the analysis phase. The thread graph for the malware sample on the right side is completely different and an analyst can get a quick overview of what actions a given samples performs. 
    </content:encoded>

    <pubDate>Tue, 25 Aug 2009 23:33:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/34-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>&quot;Towards Proactive Spam Filtering&quot;</title>
    <link>http://honeyblog.org/archives/32-Towards-Proactive-Spam-Filtering.html</link>
            <category>honeynets</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/32-Towards-Proactive-Spam-Filtering.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=32</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=32</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    &lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/spam-wc.jpg&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/spam-wc.jpg&#039;,&#039;Zoom&#039;,&#039;height=530,width=993,top=192.5,left=231,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:14 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;58&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/spam-wc.serendipityThumb.jpg&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;A common technique employed by spammers is to send spam mails with the help of botnets. In a typical setting, the spammer uses so called &lt;em&gt;template-based spamming&lt;/em&gt;: the attacker sends the bots a spam template that describes the structure of the spam message to be sent. Furthermore, the attacker sends meta-data like recipient list, subject list, and a list of URLs that are used to ﬁll in variables in the template. The bots then construct an email based on the template and the meta-data, and send this email to the targets. As a result, the actual work of handling the SMTP communication is moved from the control server to the bots. Nowadays this technique is used by most large spam botnets, like Waledac, Bobax, Rustock, Cutwail, and a lot of the other major spam botnets as Joe Stewart explained &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/secureworks.com/research/threats/botnets2009/&#039;);&quot;  href=&quot;http://secureworks.com/research/threats/botnets2009/&quot;&gt;in detail&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Since spammers nowadays use such a tactic, we can also collect spam mails in a more efficient way: Instead of waiting at the end-user&#039;s mailboxes or spamtraps for mail messages to arrive and then decide whether or not this is spam, we directly interact with the servers that are used to send spam messages. The basic idea is that we execute spambots, i.e., malicious software dedicated to sending spam emails, in a controlled (honeypot) environment and collect all email messages sent by the bots. This enables us to &lt;em&gt;directly&lt;/em&gt; interfere with botnet control servers to collect &lt;em&gt;current&lt;/em&gt; spam messages sent by a speciﬁc botnet. &lt;br /&gt;
&lt;br /&gt;
We describe this idea in more detail in a short paper that was published at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/security.dico.unimi.it/dimva2009/&#039;);&quot;  href=&quot;http://security.dico.unimi.it/dimva2009/&quot;&gt;DIMVA&#039;09&lt;/a&gt;. The paper is also &lt;a href=&quot;http://honeyblog.org/junkyard/paper/proactive-spam-short-dimva09.pdf&quot;&gt;available&lt;/a&gt; on this blog.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;: With increasing security measures in network services, remote exploitation is getting harder. As a result, attackers concentrate on more reliable attack vectors like email: victims are infected using either malicious attachments or links leading to malicious websites. Therefore eﬃcient ﬁltering and blocking methods for spam messages are needed. Unfortunately, most spam ﬁltering solutions proposed so far are reactive, they require a large amount of both ham and spam messages to eﬃciently generate rules to diﬀerentiate between both. In this paper, we introduce a more proactive approach that allows us to directly collect spam message by interacting with the spam botnet controllers. We are able to observe current spam runs and obtain a copy of latest spam messages in a fast and eﬃcient way. Based on the collected information we are able to generate templates that represent a concise summary of a spam run. The collected data can then be used to improve current spam ﬁltering techniques and develop new venues to eﬃciently ﬁlter mails.  
    </content:encoded>

    <pubDate>Fri, 31 Jul 2009 12:08:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/32-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>&quot;Automatically Generating Models for Botnet Detection&quot;</title>
    <link>http://honeyblog.org/archives/29-Automatically-Generating-Models-for-Botnet-Detection.html</link>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/29-Automatically-Generating-Models-for-Botnet-Detection.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=29</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=29</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    &lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/botdetection-wc.jpg&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/botdetection-wc.jpg&#039;,&#039;Zoom&#039;,&#039;height=555,width=837,top=180,left=309,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:12 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;72&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/botdetection-wc.serendipityThumb.jpg&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; One of the papers that we will publish at the European Symposium on Research in Computer Security (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/conferences.telecom-bretagne.eu/esorics2009/EN/home.php&#039;);&quot;  href=&quot;http://conferences.telecom-bretagne.eu/esorics2009/EN/home.php&quot;&gt;ESORICS&#039;09&lt;/a&gt;) focusses on the problem of detecting bots within a given network. Previous research focussed for example on detecting bots using human-generated signatures and anomaly detectors (e.g., &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.cyber-ta.org/pubs/botHunter-final7.pdf&#039;);&quot;  href=&quot;http://www.cyber-ta.org/pubs/botHunter-final7.pdf&quot;&gt;BotHunter&lt;/a&gt;) or correlating the activity of individual hosts in order to find machines that react in lockstep (e.g., &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/faculty.cs.tamu.edu/guofei/paper/Gu_Security08_BotMiner.pdf&#039;);&quot;  href=&quot;http://faculty.cs.tamu.edu/guofei/paper/Gu_Security08_BotMiner.pdf&quot;&gt;BotMiner&lt;/a&gt; or &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.ece.cmu.edu/~tyen/TAMD.pdf&#039;);&quot;  href=&quot;http://www.ece.cmu.edu/~tyen/TAMD.pdf&quot;&gt;TAMD&lt;/a&gt;). We present a system that &lt;em&gt;automatically&lt;/em&gt; generates signatures which encapsulate the behavior of an infected machine. The important observation is that the principle behind bots is that they receive a command from the botherder and then respond in a specific way. Using real-world traces of many botnets we show that it is possible to spot the bot responses in the network traces using a change point detection algorithm. Based on this information we can then identify the commands and we use all information to then encode a signature which we map into &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/bro-ids.org/&#039;);&quot;  href=&quot;http://bro-ids.org/&quot;&gt;Bro&lt;/a&gt; rules. Experiments in different networks show that this approach outperforms BotHunter. More information about the approach is available in the &lt;a href=&quot;http://honeyblog.org/junkyard/paper/esorics_25_botnet.pdf&quot;&gt;paper&lt;/a&gt; and all the gory details are published in a &lt;a href=&quot;http://honeyblog.org/junkyard/paper/tr_botdetection.pdf&quot;&gt;technical report&lt;/a&gt;. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;: A botnet is a network of compromised hosts that is under the control of a single, malicious entity, often called the botmaster. We present a system that aims to detect bots, independent of any prior information about the command and control channels or propagation vectors, and without requiring multiple infections for correlation. Our system relies on detection models that target the characteristic fact that every bot receives commands from the botmaster to which it responds in a speciﬁc way. These detection models are generated automatically from network trafﬁc traces recorded from actual bot instances. We have implemented the proposed approach and demonstrate that it can extract effective detection models for a variety of different bot families. These models are precise in describing the activity of bots and raise very few false positives. &lt;br /&gt;
&lt;br /&gt;
This work is a collaboration with Peter Wurzinger, Leyla Bilge, Jan Goebel, Christopher Kruegel, and Engin Kirda. And the word cloud on the top of the posting is generated with the help of &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.wordle.net/&#039;);&quot;  href=&quot;http://www.wordle.net/&quot;&gt;http://www.wordle.net/&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Fri, 17 Jul 2009 01:55:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/29-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>LEET'09 Taking Place Soon</title>
    <link>http://honeyblog.org/archives/25-LEET09-Taking-Place-Soon.html</link>
            <category>honeynets</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/25-LEET09-Taking-Place-Soon.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=25</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=25</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Join us at the 2nd USENIX Workshop on Large-Scale Exploits and Emergent Threats: Botnets, Spyware, Worms, and More (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/events/leet09/&#039;);&quot;  href=&quot;http://www.usenix.org/events/leet09/&quot;&gt;LEET&#039;09&lt;/a&gt;), which will take place in Boston, MA, on April 21, 2009. LEET &#039;09 will focus on the underlying mechanisms used to compromise and control hosts, the large-scale &quot;applications&quot; being perpetrated upon this framework, and the social and economic networks driving these threats. Sessions include Malware Analysis, Ethics in Botnet Research, Malware Behavior, and more.&lt;br /&gt;
&lt;br /&gt;
The full program is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/events/leet09/tech/&#039;);&quot;  href=&quot;http://www.usenix.org/events/leet09/tech/&quot;&gt;http://www.usenix.org/events/leet09/tech/&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
LEET &#039;09 will also include a session for Work-in-Progress reports. We encourage you to submit an abstract or proposal for a 5-minute presentation on your preliminary work to leet09wips@usenix.org.&lt;br /&gt;
&lt;br /&gt;
Connect with the broad community of researchers and practitioners who focus on worms, bots, spam, spyware, phishing, DDoS, and the ever-increasing palette of large-scale Internet-based threats in fostering the development of preliminary work in this diverse area and stimulating discussion of thought-provoking ideas.&lt;br /&gt;
&lt;br /&gt;
Find out more and register today at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/leet09/&#039;);&quot;  href=&quot;http://www.usenix.org/leet09/&quot;&gt;http://www.usenix.org/leet09/&lt;/a&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 07 Apr 2009 08:38:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/25-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Conficker Detection</title>
    <link>http://honeyblog.org/archives/24-Conficker-Detection.html</link>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/24-Conficker-Detection.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=24</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=24</wfw:commentRss>
    

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The Internet did not break down yesterday due to Conficker, it seems like the topic was hyped a bit too much by the media.&lt;br /&gt;
In case you want to quickly check whether or not your machine is infected with the worm, you can use a simple check developed by &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.joestewart.org/&#039;);&quot;  href=&quot;http://www.joestewart.org/&quot;&gt;Joe Stewart&lt;/a&gt; from &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.secureworks.com/&#039;);&quot;  href=&quot;http://www.secureworks.com/&quot;&gt;SecureWorks&lt;/a&gt;. Simply go to &lt;a href=&quot;http://honeyblog.org/junkyard/conficker/&quot;&gt;http://honeyblog.org/junkyard/conficker/&lt;/a&gt; and check which images your browser shows:&lt;br /&gt;
&lt;blockquote&gt;Conficker (aka Downadup, Kido) is known to block access to over 100 anti-virus and security websites.&lt;br /&gt;
&lt;br /&gt;
If you are blocked from loading the remote images in the first row of the top table above (AV/security sites) but not blocked from loading the remote images in the second row (websites of alternative operating systems) then your Windows PC may be infected by Conficker (or some other malicious software).&lt;br /&gt;
&lt;br /&gt;
If you can see all six images in both rows of the top table, you are either not infected by Conficker, or you may be using a proxy server, in which case you will not be able to use this test to make an accurate determination, since Conficker will be unable to block you from viewing the AV/security sites.&lt;/blockquote&gt;&lt;br /&gt;
Furthermore, the Honeynet Project recently released a paper entitled &quot;&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/honeynet.org/papers/conficker&#039;);&quot;  href=&quot;http://honeynet.org/papers/conficker&quot;&gt;Know Your Enemy: Containing Conficker&lt;/a&gt;&quot; which presents in detail several methods to detect the worm based on network characteristics,&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
The Conficker worm has infected several million computers since it first started spreading in late 2008 but attempts to mitigate Conficker have not yet proved very successful. In this paper we present several potential methods to contain Conficker. The approaches presented take advantage of the way Conficker patches infected systems, which can be used to remotely detect a compromised system. Furthermore, we demonstrate various methods to detect and remove Conficker locally and a potential vaccination tool is presented. Finally, the domainname generation mechanism for all three Conficker variants is discussed in detail and an overview of the potential for upcoming domain collisions in version .C is provided. Tools for all the ideas presented here are freely available for download including source code.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 02 Apr 2009 10:19:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/24-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>

</channel>
</rss>