<?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</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, 26 Apr 2011 21:06:18 GMT</pubDate>

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

<item>
    <title>2011 Honeynet Project Security Workshop Slides + Videos</title>
    <link>http://honeyblog.org/archives/65-2011-Honeynet-Project-Security-Workshop-Slides-+-Videos.html</link>
            <category>honeynets</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/65-2011-Honeynet-Project-Security-Workshop-Slides-+-Videos.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=65</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The slides and videos from the 2011 Honeynet Project Security Workshop (Paris) are now available! You can get the material from &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.honeynet.org/SecurityWorkshops/2011_Paris&#039;);&quot;  href=&quot;http://www.honeynet.org/SecurityWorkshops/2011_Paris&quot;&gt;http://www.honeynet.org/SecurityWorkshops/2011_Paris&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
About the workshop:&lt;blockquote&gt;The workshop brought together experts in the field of information security from around the world to share the latest advances in security research. Our members covered topics such as new honeyclients, mobile malware, new reversing techniques, VOIP attacks and even social behavior of attackers. And besides the presentation, Felix Leder and Mark Schloesser from our Giraffe chapter and Guillaume Arcas from our French chapter put up some hands on exercises that allowed participants to test their skillz.&lt;/blockquote&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 26 Apr 2011 23:06:18 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/65-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>SysSec Workshop</title>
    <link>http://honeyblog.org/archives/64-SysSec-Workshop.html</link>
            <category>admin</category>
    
    <comments>http://honeyblog.org/archives/64-SysSec-Workshop.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=64</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    It has been quite some time since I last blogged, in the past few months I mainly used &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/twitter.com/#!/thorstenholz&#039;);&quot;  href=&quot;http://twitter.com/#!/thorstenholz&quot;&gt;my Twitter account&lt;/a&gt; to publish news. Today I want to blog again since the information about the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.syssec-project.eu/&#039;);&quot;  href=&quot;http://www.syssec-project.eu/&quot;&gt;SysSec&lt;/a&gt; Network of Excellence will not fit into a single tweet. &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/syssec-project.eu&#039;);&quot;  href=&quot;http://syssec-project.eu&quot;&gt;SysSec&lt;/a&gt; is a Network of Excellence in the field of Systems Security, which has been created to build on the successful experience of the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/forward-project.eu&#039;);&quot;  href=&quot;http://forward-project.eu&quot;&gt;FORWARD&lt;/a&gt; initiative to work towards:&lt;br /&gt;
&lt;ol&gt;&lt;li&gt;creating a virtual center of excellence, to consolidate the Systems Security research community in Europe&lt;/li&gt;&lt;li&gt;promoting cybersecurity education&lt;/li&gt;&lt;li&gt;engaging a think-tank in discovering the threats and vulnerabilities of the Current and Future Internet,&lt;/li&gt;&lt;li&gt;creating an active research roadmap in the area, and&lt;/li&gt;&lt;li&gt;developing a joint working plan to conduct State-of-the-Art collaborative research.&lt;/li&gt;&lt;/ol&gt; As part of its dissemination activities, the SysSec Network of Excellence proposes to organize a workshop focused on system security research, as the first step towards creating a virtual center of excellence to consolidate the Systems Security research community in Europe. The &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.syssec-project.eu/events/1st-syssec-workshop/&#039;);&quot;  href=&quot;http://www.syssec-project.eu/events/1st-syssec-workshop/&quot;&gt;1st SysSec Workshop&lt;/a&gt; targets researchers from Europe and the rest of the World, with the short-term goal of creating a vigorous forum to map the systems security research area, with particular focus on European security communities. While this workshop invites submissions from all the research groups on systems security in the world, it encourages particularly research groups from Europe to take advantage of this opportunity. The long-term goal of this first of a series of periodic workshops, is to build a reference meeting place of the systems security community in Europe. 
    </content:encoded>

    <pubDate>Tue, 15 Feb 2011 16:35:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/64-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>The Last Line of Defense - http://tllod.com</title>
    <link>http://honeyblog.org/archives/62-The-Last-Line-of-Defense-httptllod.com.html</link>
            <category>admin</category>
            <category>malware</category>
            <category>research</category>
    
    <comments>http://honeyblog.org/archives/62-The-Last-Line-of-Defense-httptllod.com.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=62</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    I am excited to announce that the website of our start-up company LastLine, Inc., is now live at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.tllod.com&#039;);&quot;  href=&quot;http://www.tllod.com&quot;&gt;http://www.tllod.com&lt;/a&gt;. The team behind LastLine is composed of people you know from the International Secure Systems Lab (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/iseclab.org&#039;);&quot;  href=&quot;http://iseclab.org&quot;&gt;http://iseclab.org&lt;/a&gt;), we are coming from the University of California, Santa Barbara, the Vienna University of Technology (Austria), Eurecom (France), and Ruhr-University Bochum (Germany). We all have extensive expertise in malware analysis and malware countermeasures (see our &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/publications.html&#039;);&quot;  href=&quot;http://www.iseclab.org/publications.html&quot;&gt;list of publications&lt;/a&gt;) and you might know tools like &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; or &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/wepawet.iseclab.org&#039;);&quot;  href=&quot;http://wepawet.iseclab.org&quot;&gt;Wepawet&lt;/a&gt; that have been developed by us. &lt;br /&gt;
&lt;br /&gt;
LastLine, Inc., provides protection technology that is complementary to existing anti-virus software and firewalls. Our approach is based on cyber crime intelligence that we gather by analyzing millions of suspicious URLs and binaries each day. More precisely, using our advanced malware analysis tools, we pinpoint the exploit servers that are behind drive-by exploits campaigns and the command and control server that manage botnets. These servers constitute the malicious infrastructure that is used by cyber criminals to carry out their attacks.&lt;br /&gt;
&lt;br /&gt;
One of the first product we offer is &lt;em&gt;&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.tllod.com/products/llweb&#039;);&quot;  href=&quot;http://www.tllod.com/products/llweb&quot;&gt;llweb&lt;/a&gt;&lt;/em&gt;, a tool that analyzes web sites for the presence of malicious code, such as drive-by download exploits. llweb was developed by the creators of &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/wepawet.iseclab.org&#039;);&quot;  href=&quot;http://wepawet.iseclab.org&quot;&gt;Wepawet&lt;/a&gt; and you can find out more about the tool at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/tllod.com/products/llweb&#039;);&quot;  href=&quot;http://tllod.com/products/llweb&quot;&gt;http://tllod.com/products/llweb&lt;/a&gt;. We also offer several other tools and services: &lt;em&gt;llmon&lt;/em&gt; is a service that helps organizations to determine if their hosts are used to deliver or control malware. We continuously monitor whether a customer&#039;s assets participate in malicious activities, and if so, we provide detailed and early warning so that proper mitigation steps can be initiated. llmon was developed by some of the creators of &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.maliciousnetworks.org/&#039;);&quot;  href=&quot;http://www.maliciousnetworks.org/&quot;&gt;FIRE&lt;/a&gt;. Furthermore, we provide access to the list of IP addresses, domains, and URLs that we identify to be associated with malicious activity on the Internet. Customers can obtain continuously-updated intelligence, which can be leveraged internally to identify compromised hosts or configure network access control mechanisms. You can find more about our products at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/tllod.com/what&#039;);&quot;  href=&quot;http://tllod.com/what&quot;&gt;http://tllod.com/what&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
  
    </content:encoded>

    <pubDate>Thu, 01 Jul 2010 15:11:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/62-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Call for Papers: EC2ND'10</title>
    <link>http://honeyblog.org/archives/61-Call-for-Papers-EC2ND10.html</link>
            <category>admin</category>
            <category>research</category>
    
    <comments>http://honeyblog.org/archives/61-Call-for-Papers-EC2ND10.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=61</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The sixth European Conference on Computer Network Defense (&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/2010.ec2nd.org/&#039;);&quot;  href=&quot;http://2010.ec2nd.org/&quot;&gt;EC2ND&lt;/a&gt;) will be held at the Faculty of Electrical Engineering and Computer Science at Berlin Institute of Technology (TU Berlin) on October 28-29, 2010. The conference brings together researchers from academia and industry within Europe and beyond to present and discuss current topics in applied network and systems security. EC2ND 2010 invites submissions presenting novel ideas in the areas of network defense, intrusion detection and systems security. &lt;br /&gt;
&lt;br /&gt;
EC2ND 2010 specifically encourages submissions presenting work at an early stage with the intention to act as a discussion forum for innovative security research. While our goal is to solicit ideas that are not completely worked out, and might have challenging and interesting open questions, we expect submissions to be supported by some evidence of feasibility or preliminary quantitative results.&lt;br /&gt;
&lt;br /&gt;
Important dates:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Paper submission deadline:            July 2, 2010&lt;/li&gt;&lt;li&gt;Paper acceptance or rejection:        August 6, 2010&lt;/li&gt;&lt;li&gt;Final paper camera ready copy:        August 13, 2010&lt;/li&gt;&lt;li&gt;Conference dates:                     October 28-29, 2010&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
The full Call for Papers is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/2010.ec2nd.org/cfp/&#039;);&quot;  href=&quot;http://2010.ec2nd.org/cfp/&quot;&gt;http://2010.ec2nd.org/cfp/&lt;/a&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 24 Jun 2010 09:54:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/61-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Chaosradio Express #155</title>
    <link>http://honeyblog.org/archives/60-Chaosradio-Express-155.html</link>
            <category>admin</category>
            <category>honeynets</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/60-Chaosradio-Express-155.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=60</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Recently I recorded a longer podcast together with &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/tim.geekheim.de/&#039;);&quot;  href=&quot;http://tim.geekheim.de/&quot;&gt;Tim Pritlove&lt;/a&gt; on malware and botnets. It was published a few days ago as &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/chaosradio.ccc.de/cre155.html&#039;);&quot;  href=&quot;http://chaosradio.ccc.de/cre155.html&quot;&gt;Chaosradio Express #155&lt;/a&gt;. The podcast is in German and lasts for about 2.5 hours. The podcast is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/chaosradio.ccc.de/cre155.html&#039;);&quot;  href=&quot;http://chaosradio.ccc.de/cre155.html&quot;&gt;http://chaosradio.ccc.de/cre155.html&lt;/a&gt; and you can also get it via &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/itunes.apple.com/de/podcast/chaosradio-express/id135057227&#039;);&quot;  href=&quot;http://itunes.apple.com/de/podcast/chaosradio-express/id135057227&quot;&gt;iTunes&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Here the German description:&lt;br /&gt;
&lt;blockquote&gt;Malware hat sich in den letzten 10 Jahren von einem Forschungsfeld zu einer globalen Bedrohung der internationalen Dateninfrastruktur entwickelt. Botnetze stellen dabei die bedauerliche Krönung der kriminellen Aktivitäten dar und es erfordert einen großen Aufwand, diesen Systemen nachzugehen und sie wieder auszuschalten. Trotz eines fortwährenden Katz- und Mausspielchens gelingt es den Sicherheitsforschern immer wieder, große Botnetze vom Netz zu nehmen. Im Gespräch mit Tim Pritlove erläutert Thorsten Holz Geschichte und technische Hintergründe zu Malware und Botnetzen.&lt;br /&gt;
&lt;br /&gt;
Themen: wie sich Malware über die Zeit vom Experiment zum Werkzeug von Kriminellen entwickelt hat; welche Sicherheitslücken ausgenutzt werden; welche Methoden Betriebssysteme haben, sich gegen Malware zu wehren; das Layer-8-Problem; die Antiviren-Industrie; was Microsoft für seine Sicherheit getan hat; Botnetze und Spam und andere Formen der Monetarisierung; wie sich Botnetze gegen Aufklärung schützen; wie man ein Botnetz ausforscht, austrickst und lahmlegt; Botnetze aufspüren mit Honeypots; Botnetze in Behörden und Botschaften; Kommunikation und Kollaboration von Securitygruppen; technische und moralische Probleme beim Herunterfahren eines Botnets; Kooperation mit ISPs; Botnetzbekämpfung vs. Zensurinfrastruktur; Botnetze und der Mac; Konzepte für sichere Betriebssysteme; Security Usability; Automatisierte Malware Analyse.&lt;/blockquote&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 10 Jun 2010 18:07:40 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/60-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Challenge 4 of the Forensic Challenge 2010 - VoIP</title>
    <link>http://honeyblog.org/archives/59-Challenge-4-of-the-Forensic-Challenge-2010-VoIP.html</link>
            <category>honeynets</category>
    
    <comments>http://honeyblog.org/archives/59-Challenge-4-of-the-Forensic-Challenge-2010-VoIP.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=59</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Quick blog posting about the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/honeynet.org/challenges/2010_4_voip&#039;);&quot;  href=&quot;http://honeynet.org/challenges/2010_4_voip&quot;&gt;new forensic challenge&lt;/a&gt; by the Honeynet Project:&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;Challenge 4 - VoIP - (provided by Ben Reardon from the Australian and Sjur Eivind Usken from Norwegian Chapter) takes you into the world of voice communications on the Internet. VoIP with SIP is becoming the de-facto standard for voice communication on the Internet. As this technology becomes more common, malicious parties have more opportunities and stronger motives to take control of these systems to conduct nefarious activities. This Challenge is designed to examine and explore some of attributes of the SIP and RTP protocols. Enjoy the challenge.&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
You can find all info at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/honeynet.org/challenges/2010_4_voip&#039;);&quot;  href=&quot;http://honeynet.org/challenges/2010_4_voip&quot;&gt;http://honeynet.org/challenges/2010_4_voip&lt;/a&gt;. Submission deadline is June 30th 2010 - thus you still have some time to work on the challenge. You can win books, for example a signed copy of &quot;&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.amazon.com/gp/product/0321336321&#039;);&quot;  href=&quot;http://www.amazon.com/gp/product/0321336321&quot;&gt;Virtual Honeypots: From Botnet Tracking to Intrusion Detection&lt;/a&gt;&quot; by Niels and me. 
    </content:encoded>

    <pubDate>Thu, 10 Jun 2010 16:38:56 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/59-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>&quot;Is the Internet for Porn? An Insight Into the Online Adult Industry&quot;</title>
    <link>http://honeyblog.org/archives/58-Is-the-Internet-for-Porn-An-Insight-Into-the-Online-Adult-Industry.html</link>
            <category>paper</category>
            <category>research</category>
    
    <comments>http://honeyblog.org/archives/58-Is-the-Internet-for-Porn-An-Insight-Into-the-Online-Adult-Industry.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=58</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Recently, we studied an aspect of the World Wide Web that did not receive a lot of attention yet - the &lt;em&gt;online adult industry&lt;/em&gt;. Compared to traditional media, the Internet provides fast, easy, and anonymous access to the desired content. That, in turn, results in a huge number of users accessing pornographic content. To improve the understanding of this part of the Web, we performed a study of the online adult industry. As a result, we provide a detailed overview of the individual actors and roles within the online adult industry, which enables us to better understand the mechanisms with which visitors are redirected between the individual parties and how money flows between them. Furthermore, we examined the security aspects of more than 250,000 adult pages and studied, among other aspects, the prevalence of drive-by download attacks. In addition, we analyzed domain-specific security threats such as disguised traffic redirection techniques, and surveyed the hosting infrastructure of adult sites. &lt;br /&gt;
&lt;br /&gt;
&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/AdultSites-wc.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/AdultSites-wc.png&#039;,&#039;Zoom&#039;,&#039;height=450,width=847,top=232.5,left=304,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:39 --&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/AdultSites-wc.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;Lastly, we operated two adult web sites on our own. By becoming adult web site operators ourselves, we gained additional insights on unique security aspects in this domain. This enabled us to obtain a deeper understanding of the related abuse potential. We participated in adult traffic trading, and provide a detailed discussion of this unique aspect of adult web sites, including insights into the economical implications, and possible attack vectors that a malicious site operator could leverage. For example, we discovered that a malicious operator could infect more than 20,000 with a minimal investment of about $160. Furthermore, we experimentally show that a malicious site operator could benefit from domain-specific business practices that facilitate click-fraud and mass exploitation. We conclude that many participants of this industry have business models that are based on very questionable practices that could very well be abused for malicious activities and conducting cyber-crime. In fact, we found evidence that this kind of abuse is already happening in the wild.&lt;br /&gt;
&lt;br /&gt;
All details of our study are available in the  &lt;a href=&quot;http://honeyblog.org/junkyard/paper/adultSites-weis2010.pdf&quot;&gt;paper&lt;/a&gt;. The paper will be presented at the Ninth 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 2010&lt;/a&gt;). WEIS will take place on June 7/8 at Harvard University.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
The online adult industry is among the most profitable business branches on the Internet, and its web sites attract large amounts of visitors and traffic. Nevertheless, no study has yet characterized the industry’s economical and security-related structure. As cyber-criminals are motivated by financial incentives, a deeper understanding and identification of the economic actors and interdependencies in the online adult business is important for analyzing security-related aspects of this industry.&lt;br /&gt;
In this paper, we provide a survey of the different economic roles that adult web sites assume, and highlight their economic and technical features. We provide insights into security flaws and potential points of interest for cyber-criminals. We achieve this by applying a combination of automatic and manual analysis techniques to investigate the economic structure of the online adult industry and its business cases. Furthermore, we also performed several experiments to gain a better understanding of the flow of visitors to these sites and the related cash flow, and report on the lessons learned while operating adult web sites on our own.&lt;br /&gt;
&lt;br /&gt;
This paper was joint work with Gilbert Wondracek, Christian Platzer, Engin Kirda, and Christopher Kruegel, all members of the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/&#039;);&quot;  href=&quot;http://www.iseclab.org/&quot;&gt;International Secure Systems Lab&lt;/a&gt;. You can get the paper at &lt;a href=&quot;http://honeyblog.org/junkyard/paper/adultSites-weis2010.pdf&quot;&gt;http://honeyblog.org/junkyard/paper/adultSites-weis2010.pdf&lt;/a&gt;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 06 May 2010 13:47:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/58-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>USENIX LEET'10 &amp; RAID 2010</title>
    <link>http://honeyblog.org/archives/57-USENIX-LEET10-RAID-2010.html</link>
            <category>admin</category>
    
    <comments>http://honeyblog.org/archives/57-USENIX-LEET10-RAID-2010.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=57</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    A quick announcement:&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;Join us at the 3rd USENIX Workshop on Large-Scale Exploits and Emergent Threats, which will take place in San Jose, CA, on April 27, 2010. LEET &#039;10 will 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.&lt;br /&gt;
&lt;br /&gt;
The program includes:&lt;br /&gt;
-- Keynote Address: &quot;Why Don&#039;t I (Still) Trust Anything?&quot; by Jeff Moss, Founder, Black Hat and DEF CON&lt;br /&gt;
&lt;br /&gt;
-- Invited Talk: &quot;Naked Avatars and Other Cautionary Tales About MMORPG Password Stealers,&quot; by Jeff Williams, Microsoft Malware Protection Center&lt;br /&gt;
&lt;br /&gt;
-- Sessions on threat measurement and characterization, botnets, threat detection and mitigation, and more.&lt;br /&gt;
&lt;br /&gt;
Check out the full program at&lt;br /&gt;
&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/events/leet10/tech/&#039;);&quot;  href=&quot;http://www.usenix.org/events/leet10/tech/&quot;&gt;http://www.usenix.org/events/leet10/tech/&lt;/a&gt;&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;br /&gt;
&lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.usenix.org/leet10/proga&#039;);&quot;  href=&quot;http://www.usenix.org/leet10/proga&quot;&gt;http://www.usenix.org/leet10/proga&lt;/a&gt;&lt;/blockquote&gt;&lt;br /&gt;
And please note that the deadline for &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.raid2010.org/&#039;);&quot;  href=&quot;http://www.raid2010.org/&quot;&gt;RAID 2010&lt;/a&gt; has been extended to April 21, 2010. See the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.raid2010.org/call-for-participation&#039;);&quot;  href=&quot;http://www.raid2010.org/call-for-participation&quot;&gt;Call for Participation&lt;/a&gt; for more details. Looking forward to your papers!&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://honeyblog.org/archives/57-USENIX-LEET10-RAID-2010.html#extended&quot;&gt;Continue reading &quot;USENIX LEET&#039;10 &amp;amp; RAID 2010&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 15 Apr 2010 09:06:23 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/57-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Technical Report: &quot;Abusing Social Networks for Automated User Profiling&quot;</title>
    <link>http://honeyblog.org/archives/56-Technical-Report-Abusing-Social-Networks-for-Automated-User-Profiling.html</link>
            <category>paper</category>
            <category>research</category>
    
    <comments>http://honeyblog.org/archives/56-Technical-Report-Abusing-Social-Networks-for-Automated-User-Profiling.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=56</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    We recently published a &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/papers/socialabuse-TR.pdf&#039;);&quot;  href=&quot;http://www.iseclab.org/papers/socialabuse-TR.pdf&quot;&gt;technical report&lt;/a&gt; on another project related to social networks. The paper is entitled &quot;Abusing Social Networks for Automated User Profiling&quot; and we focus on automatically collecting information about users based on the information available in different networks. &lt;br /&gt;
&lt;br /&gt;
&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/userProfiling-architecture.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/userProfiling-architecture.png&#039;,&#039;Zoom&#039;,&#039;height=333,width=885,top=441,left=525,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:36 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;40&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/userProfiling-architecture.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; Imagine that you have a profile on &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.facebook.com/&#039;);&quot;  href=&quot;http://www.facebook.com/&quot;&gt;Facebook&lt;/a&gt;, on &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.linkedin.com/&#039;);&quot;  href=&quot;http://www.linkedin.com/&quot;&gt;LinkedIn&lt;/a&gt;, and on &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.myspace.com/&#039;);&quot;  href=&quot;http://www.myspace.com/&quot;&gt;MySpace&lt;/a&gt;. Perhaps you do not want to directly link these profiles, for example since you want to have a more serious profile on LinkedIn, while having a more relaxed one on MySpace and Facebook. Thus you use different pseudonym/names on the different profiles and expect that the information can not be correlated. However, there is a problem with that assumption: during the registration on the different networks, you used the same e-mail address. And a social network typically enables a user to search for e-mail addresses in order to find friends (a convenient feature, after all you want to network with your friends). An attacker can thus go ahead and search on each network for a given e-mail address, scrape the profile related to that address, and then correlate the information found on different network. At the end, an attacker can thus enrich a given e-mail address with information collected on different social networks. &lt;br /&gt;
&lt;br /&gt;
&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/userProfilingSN-wc.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/userProfilingSN-wc.png&#039;,&#039;Zoom&#039;,&#039;height=545,width=848,top=335,left=543.5,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:37 --&gt;&lt;img class=&quot;serendipity_image_right&quot; width=&quot;110&quot; height=&quot;70&quot; style=&quot;float: right; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/userProfilingSN-wc.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; An attacker can not only search for one e-mail address at a time, but typically for hundreds or even thousands. And he can not only do this once, but thousands of times per day. For example, we were able to check about 10 million e-mail addresses on Facebook per day. A spammer could use this &quot;feature&quot; to verify e-mail addresses by using Facebook as an oracle to determine whether or not a given e-mail address is valid. Furthermore, the correlation aspect is of course also a privacy problem since an attacker can find &quot;hidden&quot; information and correlate information across different networks.&lt;br /&gt;
&lt;br /&gt;
We have contacted different social networks. Facebook and XING have already addressed the problem - thanks a lot!&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
Recently, social networks such as Facebook have experienced a huge surge in popularity. The amount of personal information stored in these sites calls for appropriate security precautions to protect this data.&lt;br /&gt;
In this paper, we describe how we are able to take advantage of a common weakness, namely the fact that an attacker can query the social network for registered e-mail addresses on a large scale. Starting with a list of about 10.4 million email addresses, we were able to automatically identify more than 1.2 million user profiles associated with these addresses. By crawling these profiles, we collect publicly available personal information about each user, which we use for automated profiling (i.e., to enrich the information available from each user).&lt;br /&gt;
Finally, we propose a number of mitigation techniques to protect the user’s privacy. We have contacted the most popular providers, who acknowledged the threat and are currently implementing our countermeasures. Facebook and XING in particular have recently fixed the problem.&lt;br /&gt;
&lt;br /&gt;
The technical report is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/papers/socialabuse-TR.pdf&#039;);&quot;  href=&quot;http://www.iseclab.org/papers/socialabuse-TR.pdf&quot;&gt;http://www.iseclab.org/papers/socialabuse-TR.pdf&lt;/a&gt; and it was joint work with Marco Balduzzi, Christian Platzer, Engin Kirda, Davide Balzarotti, and Christopher Kruegel. 
    </content:encoded>

    <pubDate>Wed, 17 Mar 2010 11:37:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/56-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>Twitter Spamdetector Service</title>
    <link>http://honeyblog.org/archives/55-Twitter-Spamdetector-Service.html</link>
            <category>research</category>
    
    <comments>http://honeyblog.org/archives/55-Twitter-Spamdetector-Service.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=55</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    At the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/&#039;);&quot;  href=&quot;http://www.iseclab.org/&quot;&gt;International Secure Systems Lab&lt;/a&gt;, we have developed a couple of services like &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/wepawet.iseclab.org/&#039;);&quot;  href=&quot;http://wepawet.iseclab.org/&quot;&gt;Wepawet&lt;/a&gt;, or &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.maliciousnetworks.org/&#039;);&quot;  href=&quot;http://www.maliciousnetworks.org/&quot;&gt;FIRE&lt;/a&gt;. Lately, we have worked on a mechanism to detect spammers on &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/twitter.com/&#039;);&quot;  href=&quot;http://twitter.com/&quot;&gt;Twitter&lt;/a&gt;, a popular microblogging service. We have developed several heuristics to detect spamming profiles, and have already reported thousands of these profiles to Twitter, who then shut down these profiles. Now we have created a profile to which users can flag spammers on Twitter: the flagged accounts are added to our database, allowing us to detect profiles from campaigns we did not observe before. &lt;br /&gt;
&lt;br /&gt;
The profile is &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/twitter.com/spamdetector&#039;);&quot;  href=&quot;http://twitter.com/spamdetector&quot;&gt;@spamdetector&lt;/a&gt;, and the messages it accepts are of the format &lt;br /&gt;
&lt;blockquote&gt;&quot;@spamdetector @spamaccount&quot;&lt;/blockquote&gt;&lt;br /&gt;
Whenever you see a suspicious account, you can simply send us a notification and our system will check if this account is likely a spammer or not. This helps us to improve our heuristics, and we can help Twitter to shut down suspicious profiles, leading to a better service.&lt;br /&gt;
&lt;br /&gt;
This work was carried out by &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.cs.ucsb.edu/~gianluca/&#039;);&quot;  href=&quot;http://www.cs.ucsb.edu/~gianluca/&quot;&gt;Gianluca Stringhini&lt;/a&gt;, a PhD student at University of California, Santa Barbara, working as research assistant at the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/cs.ucsb.edu/~seclab/&#039;);&quot;  href=&quot;http://cs.ucsb.edu/~seclab/&quot;&gt;Computer Security lab&lt;/a&gt;. And you can find my tweets at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/twitter.com/thorstenholz&#039;);&quot;  href=&quot;http://twitter.com/thorstenholz&quot;&gt;@thorstenholz&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Tue, 16 Mar 2010 12:50:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/55-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<item>
    <title>&quot;Inspector Gadget: Automated Extraction of Proprietary Gadgets from Malware Binaries&quot;</title>
    <link>http://honeyblog.org/archives/54-Inspector-Gadget-Automated-Extraction-of-Proprietary-Gadgets-from-Malware-Binaries.html</link>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/54-Inspector-Gadget-Automated-Extraction-of-Proprietary-Gadgets-from-Malware-Binaries.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=54</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    When analyzing malware samples, a human analyst is typically interested in understanding/recovering a specific algorithms of the given sample. In the case of Conficker, for example, she might be interested in extracting the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/mtc.sri.com/Conficker/index.html#fig-2&#039;);&quot;  href=&quot;http://mtc.sri.com/Conficker/index.html#fig-2&quot;&gt;domain generation algorithm&lt;/a&gt; such that she can understand what domains are currently and in the future used by the malware. Or for spam bots, she might be interested in how the malware downloads spam templates, decodes them, and then generates the actual spam messages. Or for bots, she might be interested in understanding how binary updates are downloaded, decoded, and then executed.  &lt;br /&gt;
&lt;br /&gt;
&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/paper/wordclouds/InspectorGadget-wc.png&#039; onclick=&quot;F1 = window.open(&#039;/uploads/paper/wordclouds/InspectorGadget-wc.png&#039;,&#039;Zoom&#039;,&#039;height=476,width=847,top=369.5,left=544,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:38 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;110&quot; height=&quot;61&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/paper/wordclouds/InspectorGadget-wc.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; In each case, the binary itself encodes the algorithm, but it is cumbersome and hard work to understand all of this. Thus it would be useful to have a tool that enables a malware analyst to &lt;em&gt;automatically&lt;/em&gt; extract from a given binary sample the relevant algorithm related to a specific task. In a paper that will be presented 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; we introduce &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&#039;);&quot;  href=&quot;http://www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&quot;&gt;Inspector Gadget&lt;/a&gt;, a tool that implements exactly this. A gadget encapsulates all code related to a specific task and can be executed in a stand-alone fashion. A &lt;em&gt;gadget player&lt;/em&gt; can take a gadget and replay it, for example to determine which domains are currently used by Conficker, or download and decode an update for a bot binary. Furthermore, we introduce an approach to revert gadget based on a enhanced brute-force algorithm: this is useful to understand the effects of malware in detail and we can (in certain cases) also revert obfuscation algorithms, i.e., to understand what data has been exfiltrated by a given sample. The &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&#039;);&quot;  href=&quot;http://www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&quot;&gt;full paper&lt;/a&gt; has all the details and describes Inspector Gadget in more depth. And if you are interested in the topic, you should also read the paper by Caballero et al. on &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-133.html&#039;);&quot;  href=&quot;http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-133.html&quot;&gt;BCR&lt;/a&gt; (paper title is &quot;Binary Code Extraction and Interface Identification for Security Applications&quot;).&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;: &lt;br /&gt;
Unfortunately, malicious software is still an unsolved problem and a major threat on the Internet. An important component in the fight against malicious software is the analysis of malware samples: Only if an analyst understands the behavior of a given sample, she can design appropriate countermeasures. Manual approaches are frequently used to analyze certain key algorithms, such as downloading of encoded updates, or generating new DNS domains for command and control purposes.&lt;br /&gt;
In this paper, we present a novel approach to automatically extract, from a given binary executable, the algorithm related to a certain activity of the sample. We isolate and extract these instructions and generate a so-called gadget, i.e., a stand-alone component that encapsulates a specific behavior. We make sure that a gadget can autonomously perform a specific task by including all relevant code and data into the gadget such that it can be executed in a self-contained fashion.&lt;br /&gt;
Gadgets are useful entities in analyzing malicious software: In particular, they are valuable for practitioners, as understanding a certain activity that is embedded in a binary sample (e.g., the update function) is still largely a manual and complex task. Our evaluation with several real-world samples demonstrates that our approach is versatile and useful in practice.&lt;br /&gt;
&lt;br /&gt;
The full paper is available at &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&#039;);&quot;  href=&quot;http://www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&quot;&gt;http://www.iseclab.org/papers/ieee_sp10_inspector_gadget.pdf&lt;/a&gt; and will be presented in May 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;. The paper was joint work with Clemens Kolbitsch, Christopher Kruegel, and Engin Kirda - all members of the &lt;a onclick=&quot;javascript: pageTracker._trackPageview(&#039;/extlink/www.iseclab.org/&#039;);&quot;  href=&quot;http://www.iseclab.org/&quot;&gt;International Secure Systems Lab&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Fri, 12 Mar 2010 08:09:00 +0100</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/54-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
</item>
<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>&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>

</channel>
</rss>
