<?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 - paper</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>Wed, 03 Feb 2010 12:20:51 GMT</pubDate>

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

<item>
    <title>&quot;A Practical Attack to De-Anonymize Social Network Users&quot;</title>
    <link>http://honeyblog.org/archives/51-A-Practical-Attack-to-De-Anonymize-Social-Network-Users.html</link>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/51-A-Practical-Attack-to-De-Anonymize-Social-Network-Users.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=51</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    In the last couple of months, &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/&#039;);&quot;  href=&quot;http://www.iseclab.org/&quot;&gt;we&lt;/a&gt; have worked on a technique to de-anonymize users based on the way they interact with social networks. The idea behind our attack is the fact that the &lt;em&gt;group memberships&lt;/em&gt; of a user (i.e., the groups of a social network to which a user belongs) is often sufficient to uniquely identify this user. This means that there are only a few (or in the best case only one) users of a social network that are a member of exactly the same groups. &lt;br /&gt;
&lt;br /&gt;
The attack scenario is the following: a malicious website wants to de-anonymize a user, i.e., find out the real name and identity of a visitor. The attack is implemented in two phases. In a first phase, we crawl the groups of a social network to determine the members of the different groups. This is our database from which we can generate a &lt;em&gt;group fingerprint&lt;/em&gt; per user. In the second phase, we use the well-known technique of &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/bugzilla.mozilla.org/show_bug.cgi?id=147777&#039;);&quot;  href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=147777&quot;&gt;history&lt;/a&gt; &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/jeremiahgrossman.blogspot.com/2006/08/i-know-where-youve-been.html&#039;);&quot;  href=&quot;http://jeremiahgrossman.blogspot.com/2006/08/i-know-where-youve-been.html&quot;&gt;stealing&lt;/a&gt; to probe the browser&#039;s history for links to group, thus determining the group fingerprint of the visitor. Wen can then compare this fingerprint to our database and de-anonymize the visitor. Even when unique identification is not possible, then the attack might still significantly reduce the size of the set of candidates that the victim belongs to.&lt;br /&gt;
&lt;br /&gt;
As a proof-of-concept, we implemented the attack for &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.xing.com/&#039;);&quot;  href=&quot;http://www.xing.com/&quot;&gt;XING&lt;/a&gt;, a well-known &quot;Social Network for Business Professionals&quot;. Please note that this attack is not specific to XING or any other social network - it is generally applicable to different kinds of modern web applications that contain unique links for user that can be probed via history stealing. We crawled the ~7000 public groups of XING and found about 1.8 million members that belong to at least one group. These users are vulnerable to our attack and we have a &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/people/gilbert/experiment/&#039;);&quot;  href=&quot;http://www.iseclab.org/people/gilbert/experiment/&quot;&gt;demo website&lt;/a&gt; to participate in our experiment. Note that this test is only successful if you are a member of XING and a member of at least one group. If you regularly participate in groups the chances are higher that we can successfully de-anonymize you :-)&lt;br /&gt;
&lt;br /&gt;
The following pictures show the different stages of the proof-of-concept attack:&lt;center&gt;&lt;br /&gt;
&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/Experiment2.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:31 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;85&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/Experiment2.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/Experiment4.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:32 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;85&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/Experiment4.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;br /&gt;
&lt;/a&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/Experiment5-res.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:33 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;85&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/Experiment5-res.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/Experiment6-res.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:34 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;85&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/Experiment6-res.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
We have published a technical report that summarizes our preliminary results at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/papers/sonda-TR.pdf&#039;);&quot;  href=&quot;http://www.iseclab.org/papers/sonda-TR.pdf&quot;&gt;http://www.iseclab.org/papers/sonda-TR.pdf&lt;/a&gt;. In the next couple of weeks, we will finish the work on the paper and present our results at the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/oakland31.cs.virginia.edu/&#039;);&quot;  href=&quot;http://oakland31.cs.virginia.edu/&quot;&gt;31st IEEE Symposium on Security &amp;amp; Privacy&lt;/a&gt; in May. A demo of the attack is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/people/gilbert/experiment/&#039;);&quot;  href=&quot;http://www.iseclab.org/people/gilbert/experiment/&quot;&gt;http://www.iseclab.org/people/gilbert/experiment/&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Mon, 01 Feb 2010 16:43:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/51-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>Call for Papers: WEIS'10</title>
    <link>http://honeyblog.org/archives/47-Call-for-Papers-WEIS10.html</link>
            <category>admin</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/47-Call-for-Papers-WEIS10.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=47</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    I am happy to serve on the program committee of the 9th Workshop on the Economics of Information Security (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/weis2010.econinfosec.org/&#039;);&quot;  href=&quot;http://weis2010.econinfosec.org/&quot;&gt;WEIS&lt;/a&gt;). The &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/weis2010.econinfosec.org/cfp.html&#039;);&quot;  href=&quot;http://weis2010.econinfosec.org/cfp.html&quot;&gt;Call for Papers&lt;/a&gt; is now available. WEIS will take place on June 7-8, 2010 at Harvard University, Cambridge, MA, USA&lt;br /&gt;
&lt;br /&gt;
Important dates are:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Submissions due: February 22, 2010&lt;/li&gt;&lt;li&gt;Notification of acceptance: April 2, 2010&lt;/li&gt;&lt;li&gt;Workshop: June 7-8, 2010&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
Information security continues to grow in importance, as threats proliferate, privacy erodes, and attackers find new sources of value. Yet the security of information systems depends on more than just technology.  Good security requires an understanding of the incentives and tradeoffs inherent to the behavior of systems and organizations. As society’s dependence on information technology has deepened, policy makers, including the President of the United States, have taken notice.  Now more than ever, careful research is needed to accurately characterize threats and countermeasures, in both the public and private sectors.&lt;br /&gt;
&lt;br /&gt;
The Workshop on the Economics of Information Security (WEIS) is the leading forum for interdisciplinary scholarship on information security, combining expertise from the fields of economics, social science, business, law, policy and computer science. Prior workshops have explored the role of incentives between attackers and defenders, identified market failures dogging Internet security, and assessed investments in cyber-defense. This workshop will build on past efforts using empirical and analytic tools to not only understand threats, but also strengthen security through novel evaluations of available solutions. How should information risk be modeled given the constraints of rare incidence and high interdependence? How do individuals’ and organizations’ perceptions of privacy and security color their decision making?  How can we move towards a more secure information infrastructure and code base while accounting for the incentives of stakeholders? &lt;br /&gt;
&lt;br /&gt;
The full Call for Papers is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/weis2010.econinfosec.org/cfp.html&#039;);&quot;  href=&quot;http://weis2010.econinfosec.org/cfp.html&quot;&gt;http://weis2010.econinfosec.org/cfp.html&lt;/a&gt;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 18 Jan 2010 19:15:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/47-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>ADSandbox: Sandboxing JavaScript to fight Malicious Websites</title>
    <link>http://honeyblog.org/archives/43-ADSandbox-Sandboxing-JavaScript-to-fight-Malicious-Websites.html</link>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/43-ADSandbox-Sandboxing-JavaScript-to-fight-Malicious-Websites.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=43</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=43</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/adsandbox-wc.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/adsandbox-wc.png&#039;,&#039;Zoom&#039;,&#039;height=327,width=849,top=294,left=303,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:28 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;41&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/adsandbox-wc.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;Another project we were working on recently is automated analysis of JavaScript: many of the current &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/research.google.com/archive/provos-2008a.pdf&#039;);&quot;  href=&quot;http://research.google.com/archive/provos-2008a.pdf&quot;&gt;drive-by download attacks&lt;/a&gt; are triggered by heap-spraying with the help of JavaScript. In order to develop new kinds of honeyclients and to potentially also protect end-users from this threat, we developed a dynamic approach to analyze JavaScript. The basic idea is to instrument a JavaScript interpreter and profile the execution of the code. With the help of certain heuristics, we can then detect malicious code. Full details are available in the &lt;a href=&quot;http://honeyblog.org/junkyard/paper/adsandbox-sac10.pdf&quot;&gt;paper&lt;/a&gt;. The paper itself will appear at the 25th  ACM Symposium On Applied Computing (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.acm.org/conferences/sac/sac2010/&#039;);&quot;  href=&quot;http://www.acm.org/conferences/sac/sac2010/&quot;&gt;SAC&#039;10&lt;/a&gt;) in March 2010. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
We present ADSandbox, an analysis system for malicious websites that focusses on detecting attacks through JavaScript. Since, in contrast to Java, JavaScript does not have any built-in sandbox concept, the idea is to execute any embedded JavaScript within an isolated environment and log every critical action. Using heuristics on these logs, ADSandbox decides whether the site is malicious or not. In contrast to previous work, this approach combines generality with usability, since the system is executed directly on the client running the web browser before the web page is displayed. We show that we can achieve false positive rates close to 0% and false negative rates below 15% with a performance overhead of only a few seconds, what is a bit high for real time application, but supposes a great potential for future versions of our tool.&lt;br /&gt;
&lt;br /&gt;
This paper was joint work with Andreas Dewald and Felix C. Freiling. You can get the paper at &lt;a href=&quot;http://honeyblog.org/junkyard/paper/adsandbox-sac10.pdf&quot;&gt;http://honeyblog.org/junkyard/paper/adsandbox-sac10.pdf&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Wed, 30 Dec 2009 14:01:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/43-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>Call for Papers: EuroSec 2010</title>
    <link>http://honeyblog.org/archives/39-Call-for-Papers-EuroSec-2010.html</link>
            <category>admin</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/39-Call-for-Papers-EuroSec-2010.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=39</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The next edition of the European Workshop on System Security (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/eurosec-2010/&#039;);&quot;  href=&quot;http://www.iseclab.org/eurosec-2010/&quot;&gt;EuroSec 2010&lt;/a&gt;) will take place on the 13th of April, 2010, in Paris, France. Please find below the call for papers.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;About EuroSec&lt;/b&gt;:&lt;br /&gt;
EuroSec is a new workshop associated with the Annual ACM SIGOPS EuroSys conference. The workshop aims to bring together researchers, practitioners, system administrators, system programmers, and others interested in the latest advances in the security of computer systems and networks. The focus of the workshop is on novel, practical, systems-oriented work. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Important dates&lt;/b&gt;:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Paper submission: February 7, 2010 (Hard deadline, no extensions), 5pm, PST&lt;/li&gt;&lt;li&gt;Acceptance notification: March 1, 2010&lt;/li&gt;&lt;li&gt;Final paper due: March 12, 2010&lt;/li&gt;&lt;li&gt;Workshop: April 13, 2010&lt;/li&gt;&lt;/ul&gt; &lt;br /&gt;&lt;a href=&quot;http://honeyblog.org/archives/39-Call-for-Papers-EuroSec-2010.html#extended&quot;&gt;Continue reading &quot;Call for Papers: EuroSec 2010&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 25 Nov 2009 16:29:24 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/39-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>&quot;Visual Analysis of Malware Behavior Using Treemaps and Thread Graphs&quot;</title>
    <link>http://honeyblog.org/archives/33-Visual-Analysis-of-Malware-Behavior-Using-Treemaps-and-Thread-Graphs.html</link>
            <category>CWSandbox</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/33-Visual-Analysis-of-Malware-Behavior-Using-Treemaps-and-Thread-Graphs.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=33</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=33</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/visualization-wc.jpg&#039;&gt;&lt;!-- s9ymdb:15 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;54&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/visualization-wc.serendipityThumb.jpg&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;I continue the series of recently or upcoming papers with a paper we will publish at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.vizsec.org/vizsec2009/&#039;);&quot;  href=&quot;http://www.vizsec.org/vizsec2009/&quot;&gt;VizSec&#039;09&lt;/a&gt; entitled &quot;Visual Analysis of Malware Behavior Using Treemaps and Thread Graphs&quot;. In the recent years, we saw a lot of progress in the area of automated malware analysis. Nowadays tools such as &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cwsandbox.org&#039;);&quot;  href=&quot;http://cwsandbox.org&quot;&gt;CWSandbox&lt;/a&gt;, &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;, &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.threatexpert.com/&#039;);&quot;  href=&quot;http://www.threatexpert.com/&quot;&gt;ThreatExpert&lt;/a&gt;, or &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.norman.com/technology/norman_sandbox/&#039;);&quot;  href=&quot;http://www.norman.com/technology/norman_sandbox/&quot;&gt;Norman Sandbox&lt;/a&gt; are available. These tools analyze a given binary and generate a report which contains a summary of the observed behavior while executing the sample. Such reports are often quite long, it is for example not uncommon for a CWSandbox report to be longer than 100 lines. An analyst thus has to read the report in order to get an understanding of what a given sample is doing. In this paper we present an approach to visualize the behavior report with &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.cs.umd.edu/hcil/treemap-history/&#039;);&quot;  href=&quot;http://www.cs.umd.edu/hcil/treemap-history/&quot;&gt;treemaps&lt;/a&gt; and behavior graphs (i.e., visualizing the behavior of the individual threads over time). This helps to get a quick overview of what a given sample does and also samples from one malware family have a similar looking treemap/behavior graph.&lt;br /&gt;
&lt;br /&gt;
As an example, consider the following three pictures which each show the treemap generated for three distinct samples of the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/en.wikipedia.org/wiki/Bagle&#039;);&quot;  href=&quot;http://en.wikipedia.org/wiki/Bagle&quot;&gt;Bagle worm&lt;/a&gt;:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/bagle3.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/bagle3.png&#039;,&#039;Zoom&#039;,&#039;height=1217,width=1217,top=-151,left=119,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:20 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;110&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/bagle3.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/bagle2.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/bagle2.png&#039;,&#039;Zoom&#039;,&#039;height=1217,width=1217,top=-151,left=119,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:19 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;110&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/bagle2.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/bagle1.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/bagle1.png&#039;,&#039;Zoom&#039;,&#039;height=1217,width=1217,top=-151,left=119,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:18 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;110&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/bagle1.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
Each picture shows a treemap of the behavior: the x-axis depicts the type of action performed, e.g., whether the sample performed actions related to the filesystem, the registry, or the network. The y-axis devides the actions into operations, i.e., whether it was a read or write access to the registry. As you can see, the behavior of the Bagle sample is (more or less) consistent across different samples from the same family. Below you can find the visualization of two &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.f-secure.com/v-descs/swizzor.shtml&#039;);&quot;  href=&quot;http://www.f-secure.com/v-descs/swizzor.shtml&quot;&gt;Swizzor&lt;/a&gt; samples and one &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.f-secure.com/v-descs/allaple_a.shtml&#039;);&quot;  href=&quot;http://www.f-secure.com/v-descs/allaple_a.shtml&quot;&gt;Allaple&lt;/a&gt; sample.&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/swizzor2.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/swizzor2.png&#039;,&#039;Zoom&#039;,&#039;height=1217,width=1217,top=-151,left=119,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:22 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;110&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/swizzor2.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/swizzor1.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/swizzor1.png&#039;,&#039;Zoom&#039;,&#039;height=1217,width=1217,top=-151,left=119,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:21 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;110&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/swizzor1.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/allaple.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/stuff/allaple.png&#039;,&#039;Zoom&#039;,&#039;height=1217,width=1217,top=-151,left=119,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:23 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;110&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/allaple.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
Samples from the same family have a similar visualization, while samples from different families look different. This could help an analyst to quickly identify if the sample is interesting or just another small variant of a well-known family. This research will be integrated in the frontend of &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cwsandbox.org&#039;);&quot;  href=&quot;http://cwsandbox.org&quot;&gt;http://cwsandbox.org&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;: We study techniques to visualize the behavior of malicious software (malware). Our aim is to help human analysts to quickly assess and classify the nature of a new malware sample. Our techniques are based on a parametrized abstraction of detailed behavioral reports automatically generated by sandbox environments. We then explore two visualization techniques: treemaps and thread graphs. We argue that both techniques can effectively support a human analyst (a) in detecting maliciousness of software, and (b) in classifying malicious behavior.  
    </content:encoded>

    <pubDate>Fri, 21 Aug 2009 15:45:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/33-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;Bypassing Kernel Code Integrity Protection Mechanisms&quot;</title>
    <link>http://honeyblog.org/archives/30-Bypassing-Kernel-Code-Integrity-Protection-Mechanisms.html</link>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/30-Bypassing-Kernel-Code-Integrity-Protection-Mechanisms.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=30</wfw:comment>

    <wfw:commentRss>http://honeyblog.org/rss.php?version=2.0&amp;type=comments&amp;cid=30</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/RO-rootkit-wc.jpg&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/RO-rootkit-wc.jpg&#039;,&#039;Zoom&#039;,&#039;height=577,width=1015,top=169,left=220,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:16 --&gt;&lt;img class=&quot;serendipity_image_right&quot; width=&quot;110&quot; height=&quot;62&quot; style=&quot;float: right; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/RO-rootkit-wc.serendipityThumb.jpg&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;A paper that we will publish next month at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/usenix.org/events/sec09/&#039;);&quot;  href=&quot;http://usenix.org/events/sec09/&quot;&gt;USENIX Security&#039;09&lt;/a&gt; is entitled &quot;Return-Oriented Rootkits: Bypassing Kernel Code Integrity Protection Mechanisms&quot;. In return-oriented programming, an attacker re-uses existing code: he searches for short instruction sequences (typically only one instruction) which are followed by a RET. By cleverly chaining these sequences, an attacker can build a &lt;em&gt;gadget&lt;/em&gt; that then performs an actual computation, e.g., the gadget adds two operands. By combining these gadgets, an attacker can then perform arbitrary computations. Return-oriented programming was popularized by Shacham (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cseweb.ucsd.edu/~hovav/papers/s07.html&#039;);&quot;  href=&quot;http://cseweb.ucsd.edu/~hovav/papers/s07.html&quot;&gt;CCS&#039;07 paper&lt;/a&gt; targeting Linux/x86, &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cseweb.ucsd.edu/~hovav/papers/brss08.html&#039;);&quot;  href=&quot;http://cseweb.ucsd.edu/~hovav/papers/brss08.html&quot;&gt;CCS&#039;08 paper&lt;/a&gt; targeting Solaris/SPARC). In our paper we present a system to automatically find useful instructions, build gadgets, and then generate a return-oriented program for Windows as the target OS. In a case study, we show how this system can be used to implement a return-oriented rootkit, bypassing typical kernel code integrity mechanisms. The main insight here is that integrity mechanisms protect against injection of code - however, if the attacker re-uses existing code, these approaches typically fail.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;: Protecting the kernel of an operating system against attacks, especially injection of malicious code, is an important factor for implementing secure operating systems. Several kernel integrity protection mechanism were proposed recently that all have a particular shortcoming: They cannot protect against attacks in which the attacker re-uses existing code within the kernel to perform malicious computations. In this paper, we present the design and implementation of a system that fully automates the process of constructing instruction sequences that can be used by an attacker for malicious computations. We evaluate the system on different commodity operating systems and show the portability and universality of our approach. Finally, we describe the implementation of a practical attack that can bypass existing kernel integrity protection mechanisms.&lt;br /&gt;
&lt;br /&gt;
The &lt;a href=&quot;http://honeyblog.org/junkyard/paper/RO-rootkits-usenix09.pdf&quot;&gt;paper&lt;/a&gt; contains all the details and the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/pi1.informatik.uni-mannheim.de/filepool/projects/return-oriented-rootkit/measurements-ro.tgz&#039;);&quot;  href=&quot;http://pi1.informatik.uni-mannheim.de/filepool/projects/return-oriented-rootkit/measurements-ro.tgz&quot;&gt;results of our experiments&lt;/a&gt; are also available. The main part of this work was performed by Ralf Hund, it was the topic of his thesis. Furthermore, Felix Freiling helped with the project. And the word cloud was 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;Wordle&lt;/a&gt; 
    </content:encoded>

    <pubDate>Sat, 18 Jul 2009 08:13:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/30-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>Ready or Not?</title>
    <link>http://honeyblog.org/archives/26-Ready-or-Not.html</link>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/26-Ready-or-Not.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=26</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Several days ago, I finally handed in my dissertation with the title &quot;Tracking and Mitigation of Malicious Remote Control Networks&quot;. The thesis was reviewed by &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/pi1.informatik.uni-mannheim.de/~freiling&#039;);&quot;  href=&quot;http://pi1.informatik.uni-mannheim.de/~freiling&quot;&gt;Prof. Freiling&lt;/a&gt; and &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.cs.ucsb.edu/~chris/&#039;);&quot;  href=&quot;http://www.cs.ucsb.edu/~chris/&quot;&gt;Prof. Kruegel&lt;/a&gt; and my defense is at the end of the month. The thesis itself deals with different methods to study malicious remote control networks, i.e., a mechanism that enables an attacker the control over a large number of compromised machines for illicit activities. Typical examples of this kind of remote control networks are botnets and fast-flux service networks. The thesis summarizes the work from the last few years and the resulting &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/pi1.informatik.uni-mannheim.de/index.php?inc=showSnippet.php3&amp;amp;amp;action=1177511093&#039;);&quot;  href=&quot;http://pi1.informatik.uni-mannheim.de/index.php?inc=showSnippet.php3&amp;amp;action=1177511093&quot;&gt;publications&lt;/a&gt;. &lt;br /&gt;
Once my defense is over I will post a link to my thesis, it is not yet public. For now I&#039;m really happy that my PhD studies are (almost) over, looking forward to new challenges in the future :-)&lt;br /&gt;
&lt;br /&gt;
And another good news arrived today via e-mail:&lt;br /&gt;
&lt;blockquote&gt;On behalf of the 18th USENIX Security Symposium (USENIX Security &#039;09) program committee, I am delighted to inform you that your paper #108 has been accepted to appear in the conference.&lt;br /&gt;
&lt;br /&gt;
      Title: Return-Oriented Rootkits: Bypassing Kernel Code Integrity&lt;br /&gt;
             Protection Mechanisms&lt;br /&gt;
    Authors: Ralf Hund (University of Mannheim)&lt;br /&gt;
             Thorsten Holz (University of Mannheim)&lt;br /&gt;
             Felix Freiling (University of Mannheim)&lt;br /&gt;
&lt;br /&gt;
This year&#039;s selection process was very selective, and your paper was one of only 26 papers accepted out of 176 submissions.  Congratulations!&lt;/blockquote&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 13 Apr 2009 16:36:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/26-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>

</channel>
</rss>