<?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 - http://www.s9y.org/</generator>
    
    <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>SPRING Proceedings</title>
    <link>http://honeyblog.org/archives/202-SPRING-Proceedings.html</link>
            <category>general</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/202-SPRING-Proceedings.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=202</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Today the workshop &lt;a href=&quot;http://www.gi-ev.de/fachbereiche/sicherheit/fg/sidar/spring/spring3/&quot;&gt;SPRING&lt;/a&gt; took place at our lab in Mannheim. SPRING is an annual networking event for junior scientists who work in the area of reactive security. The &lt;a href=&quot;http://www.gi-ev.de/fachbereiche/sicherheit/fg/sidar/spring/spring3/program.html&quot;&gt;talks&lt;/a&gt; focussed on topics like automated malware clustering, intrusion detection systems that use peer-to-peer techniques, netflow analysis, anomaly detection on smartphones, and more. I organized the workshop, thus I&#039;m happy that it ends in a few minutes :-)&lt;br /&gt;
&lt;br /&gt;
In the next few days, we will upload all slides and also a few pictures taken during the workshop. The &lt;a href=&quot;http://honeyblog.org/junkyard/paper/SPRING-3-proceedings.pdf&quot;&gt;proceedings&lt;/a&gt; are already available. They contain a short abstract (one page) for each talk and provide an overview of the different topics covered today. 
    </content:encoded>

    <pubDate>Fri,  8 Aug 2008 18:25:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/202-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>WOOT'08 and HotSec'08</title>
    <link>http://honeyblog.org/archives/201-WOOT08-and-HotSec08.html</link>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/201-WOOT08-and-HotSec08.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=201</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Besides USENIX Security, also two interesting workshops take place this week: &lt;a href=&quot;http://www.usenix.org/events/woot08/&quot;&gt;2nd USENIX Workshop on Offensive Technologies (WOOT &#039;08)&lt;/a&gt; and &lt;a href=&quot;http://www.usenix.org/events/hotsec08/&quot;&gt;3rd USENIX Workshop on Hot Topics in Security (HotSec &#039;08)&lt;/a&gt;. Both workshops have an interesting program and the proceedings are an interesting read! My favorite paper picks:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/woot08/tech/full_papers/stinson/stinson_html/&quot;&gt;Towards Systematic Evaluation of the Evadability of Bot/Botnet Detection Methods&lt;/a&gt; by Stinson and Mitchell (WOOT&#039;08) discusses how existing botnet detection systems like Rishi, BotHunter, BotMiner, and others can be circumvented&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/hotsec08/tech/full_papers/ports/ports_html/&quot;&gt;Towards Application Security on Untrusted Operating Systems&lt;/a&gt; by Ports and Garfinkel (HotSec&#039;08) discusses how malicious behavior in each major OS subsystem can undermine application security and how this threat can possibly be mitigated&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/woot08/tech/full_papers/cova/cova_html/&quot;&gt;There Is No Free Phish: An Analysis of &quot;Free&quot; and Live Phishing Kits&lt;/a&gt; by Cova et al. (WOOT&#039;08) analyzes &quot;free&quot; phishing kits like the famous &lt;a href=&quot;http://news.netcraft.com/archives/2008/01/22/mrbrain_stealing_phish_from_fraudsters.html&quot;&gt;Mr. Brain&lt;/a&gt; kits that contain backdoors&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/woot08/tech/full_papers/drewry/drewry_html/&quot;&gt;Insecure Context Switching: Inoculating Regular Expressions for Survivability&lt;/a&gt; by Drewry and Ormandy (WOOT&#039;08) shows how regular expressions can be used in a malicious way, leading to complexity attacks&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
The full papers will be available a few days after the workshops took place. 
    </content:encoded>

    <pubDate>Tue, 29 Jul 2008 12:15:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/201-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>USENIX Security'08</title>
    <link>http://honeyblog.org/archives/200-USENIX-Security08.html</link>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/200-USENIX-Security08.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=200</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    This week, the &lt;a href=&quot;http://www.usenix.org/events/sec08/tech/&quot;&gt;17th USENIX Security Symposium&lt;/a&gt; takes place in San Jose, CA. Unfortunately I can not attend this year :-( But there are many interesting papers you should check out, for example:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/sec08/tech/provos.html&quot;&gt;All Your iFRAMEs Point to Us&lt;/a&gt; by Provos et al. analyzes the threat by malicious iframes injected into websites&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/sec08/tech/halderman.html&quot;&gt;Lest We Remember: Cold Boot Attacks on Encryption Keys&lt;/a&gt; by Halderman et al. is the paper about the now famous cold boot attack, for which the &lt;a href=&quot;http://citp.princeton.edu/memory/code/&quot;&gt;full source code&lt;/a&gt; was released last week by Jacob Appelbaum at &lt;a href=&quot;http://www.thelasthope.org/&quot;&gt;The Last HOPE&lt;/a&gt; in New York City&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/sec08/tech/oberheide.html&quot;&gt;CloudAV: N-Version Antivirus in the Network Cloud&lt;/a&gt; by Oberheide et al. deals with n-version AV-scanning (basically examining a given sample with n AV-scanners and behavior-analysis tools like CWSandbox or Norman Sandbox), thereby improving detection rates&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/sec08/tech/gu.html&quot;&gt;BotMiner: Clustering Analysis of Network Traffic for Protocol- and Structure-Independent Botnet Detection&lt;/a&gt; by Gu et al. shows how botnets can be detected by correlating netflow data, finding similar behavior within the network traffic&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.usenix.org/events/sec08/tech/litty.html&quot;&gt;Hypervisor Support for Identifying Covertly Executing Binaries&lt;/a&gt; by Litty  et al. introduces a system to detect malicious code with the help of a hypervisor built on top of Xen.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;And many others&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
The full papers will be available a few days after the conference took place. A really good conference this year with an exciting program! Looking forward to attend next year :-) 
    </content:encoded>

    <pubDate>Mon, 28 Jul 2008 12:14:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/200-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Observing Malware Outbreaks with Honeypots</title>
    <link>http://honeyblog.org/archives/199-Observing-Malware-Outbreaks-with-Honeypots.html</link>
            <category>honeynets</category>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/199-Observing-Malware-Outbreaks-with-Honeypots.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=199</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Low-interaction honeypots like Nepenthes or Amun are good at capturing autonomous spreading malware that propagates via exploiting vulnerabilities in network services: by emulating specific vulnerabilities, these honeypots trick malware into exploiting the honeypot and we can capture a copy of the malware. &lt;br /&gt;
These honeypots also allow us to observe outbreaks of new malware samples: since quite many people run Nepenthes or Amun nowadays and also send the samples to cwsandbox.org for automated malware analysis, we can correlate the submissions of many different sensors at a central location. For example, we received the malware sample with MD5 sum &lt;a href=&quot;https://cwsandbox.org/?page=report&amp;analysisid=129107&amp;password=tdztb&quot;&gt;cb032b12af742555e60124f6d7d2d2ea&lt;/a&gt; from a total of 57 different sensor at the timestamps depicted below:&lt;br /&gt;
&lt;pre&gt;&lt;br /&gt;
Timestamp               Filename&lt;br /&gt;
2008-01-10 19:36:25     grospolinacb032b12af742555e60124f6d7d2d2eauLa1AA&lt;br /&gt;
2008-01-10 22:11:47     nepenthescb032b12af742555e60124f6d7d2d2easBj96A&lt;br /&gt;
2008-01-11 00:03:32     nepenthescb032b12af742555e60124f6d7d2d2easm4aaA&lt;br /&gt;
2008-01-11 00:18:58     nepenthescb032b12af742555e60124f6d7d2d2eaA&lt;br /&gt;
2008-01-11 00:22:22     nepenthescb032b12af742555e60124f6d7d2d2eayK4gcQ&lt;br /&gt;
2008-01-11 00:22:56     nepenthescb032b12af742555e60124f6d7d2d2eadOoZcA&lt;br /&gt;
2008-01-11 00:34:36     nepenthescb032b12af742555e60124f6d7d2d2eaf92wA&lt;br /&gt;
2008-01-11 00:44:56     nepenthescb032b12af742555e60124f6d7d2d2eaBmLfOg&lt;br /&gt;
2008-01-11 00:45:09     nepenthescb032b12af742555e60124f6d7d2d2eagv4WoQ&lt;br /&gt;
2008-01-11 00:53:59     nepenthescb032b12af742555e60124f6d7d2d2eaOewZcA&lt;br /&gt;
2008-01-11 01:11:01     nepenthescb032b12af742555e60124f6d7d2d2eaQANtUA&lt;br /&gt;
2008-01-11 01:56:59     nepenthescb032b12af742555e60124f6d7d2d2eaeEtIA&lt;br /&gt;
2008-01-11 04:48:11     nepenthescb032b12af742555e60124f6d7d2d2eaYO0fA&lt;br /&gt;
2008-01-11 05:32:44     nepenthescb032b12af742555e60124f6d7d2d2eadOoZcA&lt;br /&gt;
2008-01-11 06:35:31     nepenthescb032b12af742555e60124f6d7d2d2eaf0fA&lt;br /&gt;
2008-01-11 08:21:13     nepenthescb032b12af742555e60124f6d7d2d2eaze0fA&lt;br /&gt;
2008-01-11 08:49:09     nepenthescb032b12af742555e60124f6d7d2d2eaSu4fA&lt;br /&gt;
2008-01-11 09:25:49     nepenthescb032b12af742555e60124f6d7d2d2eaanj2kA&lt;br /&gt;
2008-01-11 09:41:40     nepenthescb032b12af742555e60124f6d7d2d2eaJ8ZcA&lt;br /&gt;
2008-01-11 12:00:10     cb032b12af742555e60124f6d7d2d2ea&lt;br /&gt;
2008-01-11 13:42:14     nepenthescb032b12af742555e60124f6d7d2d2ea1E4a6A&lt;br /&gt;
2008-01-11 14:15:43     nepenthescb032b12af742555e60124f6d7d2d2eaSHkgA&lt;br /&gt;
2008-01-11 14:37:06     grospolinacb032b12af742555e60124f6d7d2d2eamKgfA&lt;br /&gt;
2008-01-11 14:38:37     nepenthescb032b12af742555e60124f6d7d2d2eabGhXGQ&lt;br /&gt;
2008-01-11 18:30:29     nepenthescb032b12af742555e60124f6d7d2d2eaMPofKg&lt;br /&gt;
2008-01-11 18:39:25     nepenthescb032b12af742555e60124f6d7d2d2eaGSGoWQ&lt;br /&gt;
2008-01-11 20:33:26     nepenthescb032b12af742555e60124f6d7d2d2eab0fA&lt;br /&gt;
2008-01-12 04:19:46     nepenthescb032b12af742555e60124f6d7d2d2eauJQiA&lt;br /&gt;
2008-01-12 12:12:12     nepenthescb032b12af742555e60124f6d7d2d2eaGDoqMQ&lt;br /&gt;
2008-01-12 14:32:15     nepenthescb032b12af742555e60124f6d7d2d2eaSIUgA&lt;br /&gt;
2008-01-13 20:37:45     nepenthescb032b12af742555e60124f6d7d2d2eaYO0fA&lt;br /&gt;
2008-01-14 17:38:54     nepenthescb032b12af742555e60124f6d7d2d2eaQ8fA&lt;br /&gt;
2008-01-14 22:26:54     grospolinacb032b12af742555e60124f6d7d2d2ea2rqiGw&lt;br /&gt;
2008-01-15 06:27:12     nepenthescb032b12af742555e60124f6d7d2d2eaM0sA&lt;br /&gt;
2008-01-15 09:32:40     nepenthescb032b12af742555e60124f6d7d2d2eaM0sA&lt;br /&gt;
2008-01-18 10:20:58     nepenthescb032b12af742555e60124f6d7d2d2eaKEuA&lt;br /&gt;
2008-01-19 02:10:38     nepenthescb032b12af742555e60124f6d7d2d2eagfofkA&lt;br /&gt;
2008-01-20 05:37:39     nepenthescb032b12af742555e60124f6d7d2d2eaxeoZcA&lt;br /&gt;
2008-01-25 09:43:36     nepenthescb032b12af742555e60124f6d7d2d2eaLvAfA&lt;br /&gt;
2008-01-29 15:36:08     nepenthescb032b12af742555e60124f6d7d2d2eaBxofsA&lt;br /&gt;
2008-01-29 20:47:39     nepenthescb032b12af742555e60124f6d7d2d2eaJ00A&lt;br /&gt;
2008-02-01 18:48:12     nepenthescb032b12af742555e60124f6d7d2d2eaEcoA&lt;br /&gt;
2008-02-02 12:24:22     nepenthescb032b12af742555e60124f6d7d2d2eawcUgLg&lt;br /&gt;
2008-02-02 19:35:56     cb032b12af742555e60124f6d7d2d2ea&lt;br /&gt;
2008-02-07 13:59:24     cb032b12af742555e60124f6d7d2d2ea.dat&lt;br /&gt;
2008-02-08 15:48:30     nepenthescb032b12af742555e60124f6d7d2d2eaGfoWA&lt;br /&gt;
2008-02-14 14:14:03     cb032b12af742555e60124f6d7d2d2eacb032b12af742555...2ea&lt;br /&gt;
2008-02-21 14:20:01     nepenthescb032b12af742555e60124f6d7d2d2eaWN0fA&lt;br /&gt;
2008-02-28 16:56:53     nepenthescb032b12af742555e60124f6d7d2d2eaoexA&lt;br /&gt;
2008-03-03 15:15:39     nepenthescb032b12af742555e60124f6d7d2d2eaA&lt;br /&gt;
2008-03-11 02:56:00     nepenthescb032b12af742555e60124f6d7d2d2eaAfA&lt;br /&gt;
2008-03-14 11:11:51     nepenthescb032b12af742555e60124f6d7d2d2eaJgfA&lt;br /&gt;
2008-03-15 17:31:37     nepenthescb032b12af742555e60124f6d7d2d2eaGGYnA&lt;br /&gt;
2008-03-20 10:55:43     nepenthescb032b12af742555e60124f6d7d2d2eacb032b1...2ea&lt;br /&gt;
2008-03-20 17:05:07     nepenthescb032b12af742555e60124f6d7d2d2eaoflA&lt;br /&gt;
2008-03-31 12:12:02     nepenthescb032b12af742555e60124f6d7d2d2eaYO0fA&lt;br /&gt;
2008-04-07 07:06:12     nepenthescb032b12af742555e60124f6d7d2d2eaxMUg3A&lt;br /&gt;
2008-04-08 02:37:22     cb032b12af742555e60124f6d7d2d2ea&lt;/pre&gt;&lt;br /&gt;
Each timestamp depicts the first point in time where the specific sensor captured a copy of the malware. As you can see, the malware outbreak happened presumably at January 10, 2008. From then on, honeypot sensors all around the world captured a copy of this specific bot. The &lt;a href=&quot;https://cwsandbox.org/?page=report&amp;analysisid=129107&amp;password=tdztb&quot;&gt;CWSandbox report&lt;/a&gt; contains more detailed information about the botnet, e.g.:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;The bot creates a file named &lt;tt&gt;C:\WINDOWS\system32\explorer.exe&lt;/tt&gt;, which is a copy of itself&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;It creates a run key for the Windows registry such that the bot is started again after a reboot&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;The C&amp;C server is located at the IP address 67.43.232.36 and listens on the TCP port 8080&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;C&amp;C channel is #wawa and the command issued by the botmaster at the time of analysis is: ipscan s.s.s dcom2 -f -s&lt;/li&gt;&lt;/ul&gt; 
    </content:encoded>

    <pubDate>Sat, 26 Jul 2008 13:05:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/199-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>DIMVA'08 Slides</title>
    <link>http://honeyblog.org/archives/198-DIMVA08-Slides.html</link>
            <category>general</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/198-DIMVA08-Slides.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=198</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    A quick follow-up to our &lt;a href=&quot;http://www.dimva2008.org/&quot;&gt;DIMVA&#039;08&lt;/a&gt; paper on &quot;&lt;a href=&quot;http://honeyblog.org/archives/192-DIMVA08-Learning-and-Classification-of-Malware-Behavior.html&quot;&gt;Learning and Classification of Malware Behavior&lt;/a&gt;&quot;: the slides from Konrad&#039;s talk are now &lt;a href=&quot;http://honeyblog.org/junkyard/paper/malware-classification-dimva08-talk.pdf&quot;&gt;available&lt;/a&gt; and provide a quick overview of the topic.&lt;right&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/malware.jpeg&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:79 --&gt;&lt;img  width=&quot;110&quot; height=&quot;92&quot; style=&quot;float: right; border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/malware.serendipityThumb.jpeg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/right&gt;&lt;br /&gt;
&lt;br /&gt;
In the near future, we will integrate the results of this paper to the webinterface of &lt;a href=&quot;http://cwsandbox.org&quot;&gt;cwsandbox.org&lt;/a&gt; - stay tuned :) 
    </content:encoded>

    <pubDate>Tue, 22 Jul 2008 13:56:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/198-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Interesting Pattern in Storm Worm Traffic</title>
    <link>http://honeyblog.org/archives/196-Interesting-Pattern-in-Storm-Worm-Traffic.html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/196-Interesting-Pattern-in-Storm-Worm-Traffic.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=196</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    &lt;a href=&quot;http://bjou.homeunix.net/blog/&quot;&gt;Björn Weiland&lt;/a&gt; recently sent me a few graphs with interesting observations he made when tracking the Storm Worm botnet as part of his thesis on detection of advanced botnets.&lt;br /&gt;
The first graph visualizes the network communication of a Storm sample when executed on a machine with a private IP address. In that configuration, the bot typically sends out spam e-mails or participates in distributed denial-of-service attacks. The x-axis shows the time, while the y-axis shows the UDP/TCP destination port number the bot communicates on:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/storm/portrange-priv1.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:76 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;1088&quot; height=&quot;488&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/storm/portrange-priv1.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
The graph shows that the bot first uses NTP to synchronize the clock of the victim&#039;s machine. Afterwards, it contacts many other machines, typically on TCP ports &lt; 33.789 (strange port number?!?). After a few minutes, it also starts with spamming (lots of connections on TCP port 25). What is interesting are all the communications that happen on higher port numbers: we can, for example, identify an IP address hosted at Intercage. This IP address is part of the static backend of the botnet. In addition, an IP address related to the University of California in San Diego (UCSD) sticks out, presumably related to their &lt;a href=&quot;http://www.usenix.org/events/leet08/tech/full_papers/kreibich/kreibich_html/&quot;&gt;Storm Worm&lt;/a&gt; &lt;a href=&quot;http://www.usenix.org/events/leet08/tech/full_papers/kanich/kanich_html/&quot;&gt;research&lt;/a&gt;. I&#039;m not yet sure what all the other IP addresses mean, but presumably all of them are also suspicious and somehow related to the botnet.&lt;br /&gt;
&lt;br /&gt;
The second graph shows the network communication of a sample executed on a machine with a public IP address. In this configuration, the bot is typically used to relay messages or host services related to the botnet. Again, the x-axis depicts a timeline, whereas the y-axis show the TCP / UDP destination port number:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/storm/portrange-pub.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:77 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;1072&quot; height=&quot;456&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/storm/portrange-pub.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
Here we can observe a completely different pattern compared to the first graph. Overall, the full port range is used, with some more dense and some more sparse parts. We can also observe more TCP communication and also quite a lot communication on TCP port 80, which is related to the web sites hosted by the botnet.&lt;br /&gt;
&lt;br /&gt;
The port range between destination port 50,000 and 51,000 is far more dense compared to lower / higher ports as the following figure shows:&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/storm/50000-51000-hist1.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:75 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;575&quot; height=&quot;475&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/storm/50000-51000-hist1.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
This port range is commonly used for RTP / RTCP as defined in &lt;a href=&quot;http://www.ietf.org/rfc/rfc4504.txt &quot;&gt;RFC 4504&lt;/a&gt; - presumably just a coincidence for Storm Worm.&lt;br /&gt;
&lt;br /&gt;
Does anybody have an explanation for the distribution of destination ports used by Storm Worm? And thanks a lot to &lt;a href=&quot;http://bjou.homeunix.net/blog/&quot;&gt;Björn&lt;/a&gt; for the permission to publish the figures! 
    </content:encoded>

    <pubDate>Mon, 21 Jul 2008 17:52:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/196-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>New Storm Campaign: Amero</title>
    <link>http://honeyblog.org/archives/197-New-Storm-Campaign-Amero.html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/197-New-Storm-Campaign-Amero.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=197</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The Storm Worm botnet changed the propagation theme again and now uses a social engineering theme that builds on the weak US dollar and the ongoing financial crisis:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/storm/storm-20080721.png&#039;&gt;&lt;!-- s9ymdb:78 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;110&quot; height=&quot;63&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/storm/storm-20080721.serendipityThumb.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
The text above the picture reads:&lt;br /&gt;
&lt;blockquote&gt;The U.S. Government began to realize the plan to replace the Dollar with the &quot;Amero&quot;, the new currency of the North American Currency Union. Canada, the United States of America and Mexico have resolved to unit in order to resist the Worldwide Financial Crysis. You can become acquainted with the plan of the implementation of Amero, just click on the icon under this text.&lt;/blockquote&gt;&lt;br /&gt;
From a technical point, nothing seems to change compared to previous versions of the binary. In the last few days, our crawler measured an effective size (i.e., how many bots are online at the moment) of the botnet between six and ten thousand machines. In total, the botnet is still bigger, we observe high churn rates between different crawls.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 21 Jul 2008 16:21:54 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/197-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Fast-Flux Data</title>
    <link>http://honeyblog.org/archives/195-Fast-Flux-Data.html</link>
            <category>general</category>
            <category>honeynets</category>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/195-Fast-Flux-Data.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=195</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Back in February, we published a paper on &lt;a href=&quot;http://honeyblog.org/archives/161-Measuring-and-Detecting-Fast-Flux-Service-Networks.html&quot;&gt;fast-flux service networks&lt;/a&gt; at &lt;a href=&quot;http://www.isoc.org/isoc/conferences/ndss/08/&quot;&gt;NDSS&#039;08&lt;/a&gt;. The basic idea behind fast-flux networks is a fast change in the mapping between a domain name and the corresponding IP addresses. The attackers use this mechanism to build a proxy-network on top of compromised machines to maintain a robust hosting infrastructure for their services. For more information on this topic, see the paper by the &lt;a href=&quot;http://honeynet.org/papers/ff/&quot;&gt;Honeynet Project&lt;/a&gt; or our &lt;a href=&quot;http://honeyblog.org/junkyard/paper/08_ff_NDSS.pdf&quot;&gt;NDSS&lt;/a&gt; paper. &lt;br /&gt;
&lt;br /&gt;
To foster research in this area, the data collected during our study is available for research purposes. Up to now, quite a few people mailed me and asked for the data. To make this process a bit more scalable and also minimize the amount of work needed at my side, we decided to simply publish all the data such that everyone can download the raw data and use it for whatever purpose. Today, I uploaded a &lt;a href=&quot;http://honeyblog.org/junkyard/stuff/fast-flux-data.tgz&quot;&gt;tarball&lt;/a&gt; which contains a summary of the fast-flux data collected over a period of several weeks. The tarball contains a potpourri of different measurements and has a total size of 7.3 MB. It contains about 55K raw &lt;a href=&quot;http://www.isc.org/sw/bind/arm95/man.dig.html&quot;&gt;dig&lt;/a&gt; lookup files and has an unpacked size of about 220 MB. The archive contains the following data:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;em&gt;storm-qavoter.com.log&lt;/em&gt;: dig lookups for domain used by the Storm Worm botnet which uses fast-flux techniques&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;em&gt;asprox-damnec-hydra.log&lt;/em&gt;: dig lookups for &lt;a href=&quot;http://www.secureworks.com/research/threats/danmecasprox/&quot;&gt;Asprox/Damnec&lt;/a&gt; botnet which also  uses fast-flux techniques&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;em&gt;lookups-ff&lt;/em&gt;: dig lookups for fast-flux domains, confirmed manually&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;em&gt;lookups-spam&lt;/em&gt;: dig lookups for various domains found in spam e-mails&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;em&gt;lookups-benign&lt;/em&gt;: dig lookups for (probable) benign domains, most of them collected via &lt;a href=&quot;http://www.dmoz.org/&quot;&gt;dmoz&lt;/a&gt; or &lt;a href=&quot;http://www.alexa.com/&quot;&gt;Alexa&lt;/a&gt;&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;em&gt;lookups-ndss&lt;/em&gt;: part of the domains used for the NDSS paper&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;em&gt;lookups-ndss-ff&lt;/em&gt;: suspected fast-flux domains from NDSS paper&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
So if you are interested in this area and want to learn more about it, just download the &lt;a href=&quot;http://honeyblog.org/junkyard/stuff/fast-flux-data.tgz&quot;&gt;archive&lt;/a&gt; (7.3 MB) and play with the files :) 
    </content:encoded>

    <pubDate>Wed, 16 Jul 2008 23:57:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/195-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>#CCpower Only Scam?</title>
    <link>http://honeyblog.org/archives/194-CCpower-Only-Scam.html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/194-CCpower-Only-Scam.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=194</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Several days ago I blogged about a compromise of our honeypots in which the attacker joined the IRC channel &lt;a href=&quot;http://honeyblog.org/archives/182-Good-ol-CCpower.html&quot;&gt;#CCpower&lt;/a&gt;. Such a channel is commonly used by attackers to trade stolen credentials like credit cards, ATM pins, social security numbers, or similar things. Again, a small excerpt from within this channel:&lt;br /&gt;
&lt;br /&gt;
&lt;tt&gt;  - USA-DUMPS: I HAVE VIRGIN USA DUMPS FOR SHOPPING (WITHOUT PIN). LOOKING FOR REAL US CASHIER FOR LONG TERM RELATIONSHIP. MY YAHOO MESSENGER ID IS : DUMPS_SELLER ! RIPPERS DON&#039;T WASTE MY TIME! CONTACT ME ONLY IF YOU&#039;RE FOR REAL. THANK YOU!.&lt;br /&gt;
&lt;br /&gt;
  - cards: Selling USA dumps for shopping /msg cards- for details..&lt;br /&gt;
&lt;br /&gt;
  - User2: Carti Fullz,Paypal Fullz,user eBay, Root,Remote Desktop, Loginuri Wells si boa Sockuri ...etc..Care esti afara sau ai ceva point de facut bani prv me!!POt sa dau Spam pe oRice BAnca NUMAI DE STATE inclusiv eBay si Paypal daca ai pont!!!.&lt;br /&gt;
&lt;br /&gt;
  - vendors: Spamming for HSBC, Halifax, CIBC. e-trade bank logins. Selling UK, USA, Swedish, Australian cvvs..&lt;br /&gt;
&lt;br /&gt;
  - HenryMtcn: Cashouting Uk BanK Logins Halifax Abbey and Natwest Share Guarranted..&lt;br /&gt;
&lt;br /&gt;
  - zoRnking: I searching good deals.. with sure (100%) cashout - out rippers - because i work with money upfront on the first deal and the get back after cashout - /msg zoRnking if you accept my rules or add my YM: zornunhackXXX@yahoo.com.&lt;br /&gt;
&lt;br /&gt;
  - MSR206: Selling atm skimmer + MSR206 with 5 blank magnetic cards , video available for checking the items pvt me for info.&lt;br /&gt;
&lt;br /&gt;
  - Zenq: Vand Carti Fresh Full Info &amp;amp; Cvv2 (AU,CA,UK,US,IT,SP,EU),Dumpsuri With Pin and Track1,Track2 and Track3 Luate Cu Cipul sau cu Gura de Skimmeri.........Logine Full (Carte + user &amp;amp; password) (BOA,RBC,Desjardins,Paypal,Intesa,Poste.it,Wamu,Wachoavia,Chase,MoneyBookers),Usere Ebay(Seller &amp;amp; Buyer)..RIPPERS OUT (My Contact ICQ = 3972973XX)&lt;/tt&gt;&lt;br /&gt;
&lt;br /&gt;
Two comments on the  &lt;a href=&quot;http://honeyblog.org/archives/182-Good-ol-CCpower.html#comments&quot;&gt;previous blog entry&lt;/a&gt; pointed out that these channels are commonly used for scams. The first one:&lt;br /&gt;
&lt;blockquote&gt;And for the article, I was hanging around on different ccpower networks since the beginning, 90% of these deals are ripoffs. Poor scum nigerians and romanians try to make 20$ deals by ripping eachother off. This is just a PUG what you find on undernet and different networks like unixirc, linuxirc. These people not even criminals just losers in life. I wouldn&#039;t bother wasting too much time for watching them. Won&#039;t do any good. You will never find any serious criminal group on the internet, since their trust builds in real life. &lt;/blockquote&gt;&lt;br /&gt;
And the second one:&lt;br /&gt;
&lt;blockquote&gt;lol he said the truth!! most of them are rippers and scum bags..and yes, trust is built in real life not on internet!&lt;/blockquote&gt;&lt;br /&gt;
Does anybody have more information on this topic, for example evidence that the trading activity in these channels is commonly scam and also some kind of proof? I am interested in this topic since the implication would be that the paper by Franklin et al. on the underground economy (&quot;&lt;a href=&quot;http://www.icir.org/vern/papers/miscreant-wealth.ccs07.pdf&quot;&gt;An Inquiry into the Nature and Causes of the Wealth of Internet Miscreants&lt;/a&gt;&quot;) is not completely right - it would greatly overestimate the real size of the underground economy. Please leave a comment or send me an e-mail to thorsten.holz [at] gmail.com. 
    </content:encoded>

    <pubDate>Tue, 15 Jul 2008 10:32:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/194-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Survival of the Fittest</title>
    <link>http://honeyblog.org/archives/193-Survival-of-the-Fittest.html</link>
            <category>honeynets</category>
    
    <comments>http://honeyblog.org/archives/193-Survival-of-the-Fittest.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=193</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The &lt;a href=&quot;http://isc.sans.org/&quot;&gt;Internet Storm Center&lt;/a&gt; blogged about the &lt;a href=&quot;http://isc.sans.org/diary.html?storyid=4721&quot;&gt;Survival Time on the Internet&lt;/a&gt; today. The &lt;a href=&quot;http://isc.sans.org/survivaltime.html&quot;&gt;survival time&lt;/a&gt; is defined as:&lt;br /&gt;
&lt;blockquote&gt;The survivaltime is calculated as the average time between reports for an average target IP address. If you are assuming that most of these reports are generated by worms that attempt to propagate, an unpatched system would be infected by such a probe.&lt;br /&gt;
The average time between probes will vary widely from network to network. Some of our submitters subscribe to ISPs which block ports commonly used by worms. As a result, these submitters report a much longer &#039;survival time&#039;. On the other hand, University Networks and users of high speed internet services are frequently targeted with additional scans from malware like bots. If you are connected to such a network, your &#039;survival time&#039; will be much smaller.&lt;br /&gt;
The main issue here is of course that the time to download critical patches will exceed this survival time.&lt;/blockquote&gt;&lt;br /&gt;
With the help of honeypots, we can measure the survival time. For example, we can use low-interaction honeypot such as &lt;a href=&quot;http://nepenthes.mwcollect.org&quot;&gt;nepenthes&lt;/a&gt; or &lt;a href=&quot;http://amunhoney.sourceforge.net/&quot;&gt;amun&lt;/a&gt; that emulate common network-based vulnerabilities and deploy them at different locations. The average time it takes to download the first binary is an estimation of the survival time: The honeypots emulate known vulnerabilities and are thus exploited by different kinds of autonomous spreading malware - similar to an unpatched system. At our lab, we deployed ten honeypots in different network ranges and measured different things as I&#039;ll explain with the following graphs. These are all based on measurements between August 2007 and July 2008.&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/nepenthes/atdlpersensor.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:65 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;500&quot; height=&quot;250&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/nepenthes/atdlpersensor.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
This plot shows the total number of attacks (blue) and of downloads (red) per sensor for the measurement period. We see that there are huge differences depending on the network location (e.g., whether or not the ISP filters specific ports). Furthermore, not all attacks are successful and we also observed quite a lot failed attacks.&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/nepenthes/atdlperhour.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:70 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;500&quot; height=&quot;250&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/nepenthes/atdlperhour.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
This plot shows the percentage of attacks (red) and downloads (blue) per time of day. We can observe a clear diurnal pattern: lower attack volume during the night and higher attack volume during the day, following the typical behavior of humans.&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/nepenthes/atdlperweekday.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:66 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;500&quot; height=&quot;250&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/nepenthes/atdlperweekday.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
This plot shows the attacks (blue) and the downloads (red) per weekday for all sensors during the measurement period. The values are given in percentage of the sum of all attacks/downloads over the chosen period of time. The attack traffic is slightly higher during the weekends.&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/nepenthes/sameasnisp.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:68 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;500&quot; height=&quot;250&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/nepenthes/sameasnisp.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
Another interesting observation is whether or not the attacks originate from the same ASN as the honeypot as depicted in the above picture. The figure shows the percentage of attacks coming from the same ISP as the honeypot, e.g., for sensor 1, about 90% of the attacks originate from machines within the same autonomous system. The graph can be interpreted as many attacks being &lt;em&gt;local&lt;/em&gt; - which makes sense since autonomous spreading malware often prefers to propagate locally. In some ASNs, however, it seems like most attacks originate from other ASNs.&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/nepenthes/firstdownloadtime.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:67 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;500&quot; height=&quot;250&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/nepenthes/firstdownloadtime.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
Finally, this graph shows an estimation of the survival time: The graph shows the average amount of time for the honeypot to be attacked successfully. Red bars are honeypots with a static IP address, thus we have only one measurement point for these honeypots. For the blue bars, each honeypot had a dynamic IP address, e.g., a disconnect every 24 hours. The bar depicts the average time from obtaining a new DHCP lease to first download which can be interpreted as the time it would take for an unpatched system to be compromised. Compared to the survival time from the Internet Storm Center which is currently &lt;a href=&quot;http://isc.sans.org/survivaltime.html&quot;&gt;below five minutes&lt;/a&gt;, we measure a higher survival time. However, the time is still short and you need to patch a system before taking it online.&lt;br /&gt;
&lt;br /&gt;
More information and many more graphs are available in the &lt;a href=&quot;http://pi1.informatik.uni-mannheim.de/filepool/theses/diplomarbeit-2007-itzel.pdf&quot;&gt;thesis&lt;/a&gt; from Laura Itzel (unfortunately in German only).&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Update&lt;/em&gt;: I updated the description of the fourth figure to explain it a bit better for non-German speaking readers. 
    </content:encoded>

    <pubDate>Mon, 14 Jul 2008 20:47:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/193-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>DIMVA'08: &quot;Learning and Classification of Malware Behavior&quot;</title>
    <link>http://honeyblog.org/archives/192-DIMVA08-Learning-and-Classification-of-Malware-Behavior.html</link>
            <category>malware</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/192-DIMVA08-Learning-and-Classification-of-Malware-Behavior.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=192</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Today and tomorrow &lt;a href=&quot;http://www.dimva2008.org/&quot;&gt;DIMVA&#039;08&lt;/a&gt; takes place in Paris. DIMVA&#039;08 is the Fifth Conference on Detection of Intrusions and Malware &amp;amp; Vulnerability Assessment and organized by the special interest group &lt;a href=&quot;http://www.gi-fg-sidar.de/&quot;&gt;SIDAR&lt;/a&gt; of the &lt;a href=&quot;http://www.gi-ev.de/english/at-a-glance/&quot;&gt;German Informatics Society (GI)&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Our paper entitled &quot;&lt;a href=&quot;http://honeyblog.org/junkyard/paper/malware-classification-dimva08.pdf&quot;&gt;Learning and Classification of Malware Behavior&lt;/a&gt;&quot; is a joint work with &lt;a href=&quot;http://www.mlsec.org/&quot;&gt;Konrad Rieck&lt;/a&gt;, &lt;a href=&quot;http://consolo.de/html/default.php&quot;&gt;Carsten Willems&lt;/a&gt;, Patrick Düssel, &lt;a href=&quot;http://ida.first.fraunhofer.de/~laskov/&quot;&gt;Pavel Laskov&lt;/a&gt;, and &lt;a href=&quot;http://pi1.informatik.uni-mannheim.de/~freiling&quot;&gt;Felix Freiling&lt;/a&gt;. The paper deals with malware classification, i.e., how to automatically learn malware families using labels. We use (noisy) labels by an anti-virus product and then apply machine learning algorithms to classify malware based on execution traces generated with the help of &lt;a href=&quot;http://cwsandbox.org&quot;&gt;CWSandbox&lt;/a&gt;. In an experiment with over 3,000 previously &lt;em&gt;undetected&lt;/em&gt; malware binaries, our system correctly predicted almost 70% of labels assigned by an anti-virus scanner &lt;em&gt;four weeks later&lt;/em&gt;. Our method also detects unknown behavior, so that malware families not present in the learning corpus are correctly identified as unknown. The analysis of prominent features inferred by our discriminative models has shown interesting similarities between malware families; in particular, we have discovered that &lt;a href=&quot;http://www.sophos.com/security/analyses/viruses-and-spyware/w32doomberb.html&quot;&gt;Doomber&lt;/a&gt; and &lt;a href=&quot;http://www.sophos.com/security/analyses/viruses-and-spyware/w32gobota.html&quot;&gt;Gobot&lt;/a&gt; worms derive from the same origin, with Doomber being an extension of Gobot - all in an automated way.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
Malicious software in form of Internet worms, computer viruses, and Trojan horses poses a major threat to the security of networked systems. The diversity and amount of its variants severely undermine the effectiveness of classical signature-based detection. Yet variants of malware families share typical behavioral patterns reflecting its origin and purpose. We aim to exploit these shared patterns for classification of malware and propose a method for learning and discrimination of malware behavior. Our method proceeds in three stages: (a) behavior of collected malware is monitored in a sandbox environment, (b) based on a corpus of malware labeled by an anti-virus scanner a malware behavior classifier is trained using learning techniques and (c) discriminative features of the behavior models are ranked for explanation of classification decisions. Experiments with different heterogeneous test data collected over several months using honeypots demonstrate the effectiveness of our method, especially in detecting novel instances of malware families previously not recognized by commercial anti-virus software.&lt;br /&gt;
&lt;br /&gt;
The full paper is now &lt;a href=&quot;http://honeyblog.org/junkyard/paper/malware-classification-dimva08.pdf&quot;&gt;available&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Thu, 10 Jul 2008 10:06:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/192-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Storm Worm: World War III?</title>
    <link>http://honeyblog.org/archives/191-Storm-Worm-World-War-III.html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/191-Storm-Worm-World-War-III.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=191</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Tonight the Storm Worm botnet changed the propagation theme again. They have a bogus story, but an interesting picture:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a class=&#039;serendipity_image_link&#039; href=&#039;http://honeyblog.org/uploads/stuff/storm/storm-20080709-small.png&#039; target=&quot;_blank&quot;&gt;&lt;!-- s9ymdb:64 --&gt;&lt;img class=&quot;serendipity_image_center&quot; width=&quot;200&quot; height=&quot;145&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px;&quot; src=&quot;http://honeyblog.org/uploads/stuff/storm/storm-20080709-small.serendipityThumb.png&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/center&gt;&lt;br /&gt;
&lt;blockquote&gt;Just now US Army&#039;s Delta Force and U.S. Air Force have invaded Iran. Approximately 20000 soldiers crossed the border into Iran and broke down the Iran&#039;s Army resistance. The video made by US soldier was received today morning. Click on the video to see first minutes of the beginning of the World War III. God save us.&lt;/blockquote&gt;&lt;br /&gt;
The directory structure of the website is similar to the previous campaigns:&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;A file called ind.php is included which contains a couple of exploits for common web browser vulnerabilities.&lt;/li&gt;&lt;li&gt;The actual Storm Worm binary is called iran_occupation.exe and it behaves similar to previous versions&lt;/li&gt;&lt;/ul&gt;So actually nothing really new at the botnet side...&lt;br /&gt;
&lt;em&gt;Warning&lt;/em&gt;: Please do not visit the website visible in the screenshot, it may harm your computer. 
    </content:encoded>

    <pubDate>Wed,  9 Jul 2008 07:26:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/191-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Sicherheit'08: &quot;Monkey-Spider: Detecting Malicious Websites with Low-Interaction Honeyclients&quot;</title>
    <link>http://honeyblog.org/archives/190-Sicherheit08-Monkey-Spider-Detecting-Malicious-Websites-with-Low-Interaction-Honeyclients.html</link>
            <category>honeynets</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/190-Sicherheit08-Monkey-Spider-Detecting-Malicious-Websites-with-Low-Interaction-Honeyclients.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=190</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Back in April, our paper on low-interaction, client-side honeypots entitled &quot;&lt;a href=&quot;http://honeyblog.org/junkyard/paper/monkey-spider-Sicherheit08.pdf&quot;&gt;Monkey-Spider: Detecting Malicious Websites with Low-Interaction Honeyclients&lt;/a&gt;&quot; was published at &lt;a href=&quot;http://www.sicherheit2008.de/&quot;&gt;Sicherheit&#039;08&lt;/a&gt;, the main security conference for the German speaking community. The paper presents a client-side honeypot that can be used to detect malicious web sites. The basic idea is to use the crawler &lt;a href=&quot;http://crawler.archive.org/&quot;&gt;Heritrix&lt;/a&gt; to download content efficiently and then analyze the downloaded content with different means, e.g., AV scanners, CWSandbox, or other tools. To our surprise, the paper won the best paper award of the conference :-)&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
Client-side attacks are on the rise: malicious websites that exploit vulnerabilities in the visitor’s browser are posing a serious threat to client security, compromising innocent users who visit these sites without having a patched web browser. Currently, there is neither a freely available comprehensive database of threats on the Web nor sufficient freely available tools to build such a database. In this work, we introduce the Monkey-Spider project. Utilizing it as a client honeypot, we portray the challenge in such an approach and evaluate our system as a high-speed, Internet-scale analysis tool to build a database of threats found in the wild. Furthermore, we evaluate the system by analyzing different crawls performed during a period of three months and present the lessons learned. &lt;br /&gt;
&lt;br /&gt;
The full paper is now also &lt;a href=&quot;http://honeyblog.org/junkyard/paper/monkey-spider-Sicherheit08.pdf&quot;&gt;available for download&lt;/a&gt; and the software is published at SourceForge: &lt;a href=&quot;http://monkeyspider.sourceforge.net/&quot;&gt;http://monkeyspider.sourceforge.net/&lt;/a&gt;. The software is released under the terms of GPLv3 and the maintainer is Ali Ikinci (ali at ikinci dot info). 
    </content:encoded>

    <pubDate>Sun,  6 Jul 2008 19:55:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/190-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>WEIS'08: &quot;Studying Malicious Websites and the Underground Economy on the Chinese Web&quot;</title>
    <link>http://honeyblog.org/archives/189-WEIS08-Studying-Malicious-Websites-and-the-Underground-Economy-on-the-Chinese-Web.html</link>
            <category>honeynets</category>
            <category>paper</category>
    
    <comments>http://honeyblog.org/archives/189-WEIS08-Studying-Malicious-Websites-and-the-Underground-Economy-on-the-Chinese-Web.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=189</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    The &lt;a href=&quot;http://weis2008.econinfosec.org/&quot;&gt;7th Workshop on the Economics of Information Security&lt;/a&gt; (WEIS&#039;08) took place last week at Dartmouth College&#039;s Tuck School of Business. Several interesting papers like &quot;&lt;a href=&quot;http://weis2008.econinfosec.org/papers/MooreSecurity.pdf&quot;&gt;Security Economics and European Policy&lt;/a&gt;&quot;, &quot;&lt;a href=&quot;http://weis2008.econinfosec.org/papers/Romanosky.pdf&quot;&gt;Do Data Breach Disclosure Laws Reduce Identity Theft?&lt;/a&gt;&quot;, or &quot;&lt;a href=&quot;http://weis2008.econinfosec.org/papers/MooreImpact.pdf&quot;&gt;The Impact of Incentives on Notice and Take-down&lt;/a&gt;&quot; were presented during the workshop. Our paper entitled &quot;&lt;a href=&quot;http://honeyblog.org/junkyard/paper/www-china-WEIS08.pdf&quot;&gt;Studying Malicious Websites and the Underground Economy on the Chinese Web&lt;/a&gt;&quot; deals with several aspects of the underground economy within China&#039;s part of the World Wide Web. Amongst other techniques, we use client-side honeypots to study malicious websites.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Abstract&lt;/b&gt;:&lt;br /&gt;
The World Wide Web gains more and more popularity within China with more than 1.31 million websites on the Chinese Web in June 2007. Driven by the economic profits, cyber criminals are on the rise and use the Web to exploit innocent users. In fact, a real underground black market with thousand of participants has developed which brings together malicious users who trade exploits, malware, virtual assets, stolen credentials, and more. In this paper, we provide a detailed overview of this underground black market and present a model to describe the market. We substantiate our model with the help of measurement results within the Chinese Web. First, we show that the amount of virtual assets traded on this underground market is huge. Second, our research proves that a significant amount of websites within China’s part of the Web contain some kind of malicious content: our measurements reveal that about 1.49% of the examined sites contain malicious content that tries to attack the visitor’s browser. &lt;br /&gt;
&lt;br /&gt;
The paper is a collaboration with several researchers from China (Jianwei Zhuge, Chengyu Song, Jinpeng Guo, Xinhui Han, and Wei Zou) and a revised version of our &lt;a href=&quot;http://honeyblog.org/archives/147-Technical-Report-Studying-Malicious-Websites-and-the-Underground-Economy-on-the-Chinese-Web.html&quot;&gt;technical report&lt;/a&gt; on the same topic. The full version of the paper is now &lt;a href=&quot;http://honeyblog.org/junkyard/paper/www-china-WEIS08.pdf&quot;&gt;available&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://honeyblog.org/archives/189-WEIS08-Studying-Malicious-Websites-and-the-Underground-Economy-on-the-Chinese-Web.html#extended&quot;&gt;Continue reading &quot;WEIS&#039;08: &amp;quot;Studying Malicious Websites and the Underground Economy on the Chinese Web&amp;quot;&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri,  4 Jul 2008 10:32:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/189-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>
<item>
    <title>Fast-Flux Techniques in .mobi</title>
    <link>http://honeyblog.org/archives/188-Fast-Flux-Techniques-in-.mobi.html</link>
            <category>malware</category>
    
    <comments>http://honeyblog.org/archives/188-Fast-Flux-Techniques-in-.mobi.html#comments</comments>
    <wfw:comment>http://honeyblog.org/wfwcomment.php?cid=188</wfw:comment>

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

    <author>nospam@example.com (Thorsten Holz)</author>
    <content:encoded>
    Danmec/Asprox is an &lt;a href=&quot;http://www.secureworks.com/research/threats/danmecasprox/&quot;&gt;SQL injection attack tool&lt;/a&gt; that is responsible for some aspects of the recent wave of SQL injections (&lt;a href=&quot;http://www.shadowserver.org/wiki/pmwiki.php?n=Calendar.20080514&quot;&gt;full list maintained by ShadowServer&lt;/a&gt;). This malware also uses &lt;a href=&quot;http://honeynet.org/papers/ff/&quot;&gt;fast-flux&lt;/a&gt; &lt;a href=&quot;https://honeyblog.org/archives/161-Measuring-and-Detecting-Fast-Flux-Service-Networks.html&quot;&gt;techniques&lt;/a&gt; to host some facets of the attacks. Since a few days, the attackers also use the .mobi TLD - the first time I see this TLD being abused this way by malware. The following listing shows the results of a DNS lookup for one of the .mobi domains:&lt;br /&gt;
&lt;blockquote&gt;$ dig allocbn.mobi&lt;br /&gt;
&lt;br /&gt;
; &lt;&lt;&gt;&gt; DiG 9.3.4 &lt;&lt;&gt;&gt; allocbn.mobi&lt;br /&gt;
;; global options:  printcmd&lt;br /&gt;
;; Got answer:&lt;br /&gt;
;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 26203&lt;br /&gt;
;; flags: qr rd ra; QUERY: 1, ANSWER: 14, AUTHORITY: 4, ADDITIONAL: 0&lt;br /&gt;
&lt;br /&gt;
;; QUESTION SECTION:&lt;br /&gt;
;allocbn.mobi.                  IN      A&lt;br /&gt;
&lt;br /&gt;
;; ANSWER SECTION:&lt;br /&gt;
allocbn.mobi.           600     IN      A       200.167.230.85 &lt;br /&gt;
allocbn.mobi.           600     IN      A       69.247.175.135&lt;br /&gt;
allocbn.mobi.           600     IN      A       71.56.42.87&lt;br /&gt;
allocbn.mobi.           600     IN      A       72.187.108.240&lt;br /&gt;
allocbn.mobi.           600     IN      A       74.138.199.132&lt;br /&gt;
allocbn.mobi.           600     IN      A       75.66.193.0&lt;br /&gt;
allocbn.mobi.           600     IN      A       75.143.150.108 &lt;br /&gt;
allocbn.mobi.           600     IN      A       76.175.178.111&lt;br /&gt;
allocbn.mobi.           600     IN      A       98.165.213.34&lt;br /&gt;
allocbn.mobi.           600     IN      A       98.192.74.13&lt;br /&gt;
allocbn.mobi.           600     IN      A       98.223.61.12&lt;br /&gt;
allocbn.mobi.           600     IN      A       99.233.217.232&lt;br /&gt;
allocbn.mobi.           600     IN      A       118.160.173.122&lt;br /&gt;
allocbn.mobi.           600     IN      A       190.18.116.54&lt;/blockquote&gt;&lt;br /&gt;
The DNS answer has a short time to live (600 seconds - 10 minutes) and the IP addresses are located in many different networks - a typical sign for fast-flux techniques. Most IP addresses are located in dial-up networks like Comcast and Roadrunner, presumably these machines are infected and compromised machines. When doing a DNS lookup a couple of minutes later, a different set of IP addresses is returned:&lt;br /&gt;
&lt;blockquote&gt;;; ANSWER SECTION:&lt;br /&gt;
allocbn.mobi.           493     IN      A       208.107.82.31 [NEW]&lt;br /&gt;
allocbn.mobi.           493     IN      A       71.56.42.87&lt;br /&gt;
allocbn.mobi.           493     IN      A       72.177.224.125 [NEW]&lt;br /&gt;
allocbn.mobi.           493     IN      A       72.187.175.42 [NEW]&lt;br /&gt;
allocbn.mobi.           493     IN      A       75.143.150.108&lt;br /&gt;
allocbn.mobi.           493     IN      A       76.171.151.145 [NEW]&lt;br /&gt;
allocbn.mobi.           493     IN      A       76.175.178.111&lt;br /&gt;
allocbn.mobi.           493     IN      A       81.203.14.159 [NEW]&lt;br /&gt;
allocbn.mobi.           493     IN      A       92.233.227.123 [NEW]&lt;br /&gt;
allocbn.mobi.           493     IN      A       98.165.213.34&lt;br /&gt;
allocbn.mobi.           493     IN      A       98.192.74.13&lt;br /&gt;
allocbn.mobi.           493     IN      A       98.223.61.12&lt;br /&gt;
allocbn.mobi.           493     IN      A       99.233.217.232&lt;br /&gt;
allocbn.mobi.           493     IN      A       156.34.132.62 [NEW]&lt;/blockquote&gt;&lt;br /&gt;
This indicates the &quot;fluxiness&quot; of the domain. By DNS mining, i.e., performing DNS lookups of this domain every TTL +1 seconds, we can observe the botnet behind this attack. In the past week, we found about 1,000 unique bot IP addresses this way. 
    </content:encoded>

    <pubDate>Thu,  3 Jul 2008 16:00:00 +0200</pubDate>
    <guid isPermaLink="false">http://honeyblog.org/archives/188-guid.html</guid>
    <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/</creativeCommons:license>
</item>

</channel>
</rss>