<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: The art of unpacking Conficker worm</title>
	<atom:link href="http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/</link>
	<description>Real Time Network Protection</description>
	<lastBuildDate>Wed, 17 Mar 2010 02:24:28 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Computer Repair</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-2107</link>
		<dc:creator>Computer Repair</dc:creator>
		<pubDate>Thu, 17 Sep 2009 09:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-2107</guid>
		<description>Over the past two years, rarely did a worm get as much attention that Conficker (aka Downadup) is getting now. Its last variant, the infamous W32/Conficker.C, which surfaced in early March and is set to time-bomb on April 1, is literally all over the media. Of course, its features are well known and documented and some papers (such as SRI’s excellent analysis and a blog post from Sourcefire) even give interesting insights on the reverse engineering process. Indeed, while understanding the behavior of the malware is important to most people, learning how to understand it is even more important to some. Does the fable of the fisherman who gives the hungry man a fishing rod rather than a fish sound familiar?</description>
		<content:encoded><![CDATA[<p>Over the past two years, rarely did a worm get as much attention that Conficker (aka Downadup) is getting now. Its last variant, the infamous W32/Conficker.C, which surfaced in early March and is set to time-bomb on April 1, is literally all over the media. Of course, its features are well known and documented and some papers (such as SRI’s excellent analysis and a blog post from Sourcefire) even give interesting insights on the reverse engineering process. Indeed, while understanding the behavior of the malware is important to most people, learning how to understand it is even more important to some. Does the fable of the fisherman who gives the hungry man a fishing rod rather than a fish sound familiar?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniele Salatti</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-418</link>
		<dc:creator>Daniele Salatti</dc:creator>
		<pubDate>Thu, 07 May 2009 12:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-418</guid>
		<description>Hi Rex,
I&#039;m trying to use this guide to unpack a variant of Conficker/Downadup that infected my work computer. This version uses rundll32 to run (rundll32.exe virus.ql,random_string).
While I haven&#039;t still removed it from the system (we can&#039;t find the process that creates At1, At2,...Atn scheduled tasks on the computer), I have got a copy of the dll (I also deleted it, but it comes back again after a while).
Then I have tryed to unpack it...
This version isn&#039;t packed with UPX, so I have edited it with CFF Ecplorer and loaded it into OllyDbg and IDA (the free version).
The problem is, I wasn&#039;t able to skip all those bad branches. Ok, it was night and I was tyred. Today I&#039;ll try again. I want to learn how to do those kind of analysis. Thank you for this post!</description>
		<content:encoded><![CDATA[<p>Hi Rex,<br />
I&#8217;m trying to use this guide to unpack a variant of Conficker/Downadup that infected my work computer. This version uses rundll32 to run (rundll32.exe virus.ql,random_string).<br />
While I haven&#8217;t still removed it from the system (we can&#8217;t find the process that creates At1, At2,&#8230;Atn scheduled tasks on the computer), I have got a copy of the dll (I also deleted it, but it comes back again after a while).<br />
Then I have tryed to unpack it&#8230;<br />
This version isn&#8217;t packed with UPX, so I have edited it with CFF Ecplorer and loaded it into OllyDbg and IDA (the free version).<br />
The problem is, I wasn&#8217;t able to skip all those bad branches. Ok, it was night and I was tyred. Today I&#8217;ll try again. I want to learn how to do those kind of analysis. Thank you for this post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rex</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-276</link>
		<dc:creator>Rex</dc:creator>
		<pubDate>Thu, 23 Apr 2009 02:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-276</guid>
		<description>Hi John,

You can also check AV websites for detailed analysis of Conficker/Downadup variants. 
SRI also has very detailed information about reversing Conficker.
Its important to understand the overall behavior of the worm before tracing the code, because not all the code will be passed on every execution (there are some conditional checks before running other functionalities)
Some variants work by using rundll32 as: rundll32.exe virus.dll,randomstring
while other would need to play around the value of dwReason to continue the execution.
Also watch out for the antidebug/anti VM codes.

AV companies usually have copies of this worm, so check your contacts.
Or maybe you should try other malware source, like offensivecomputing or
malwaredomainlist, etc.

Good luck.

-Rex</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>You can also check AV websites for detailed analysis of Conficker/Downadup variants.<br />
SRI also has very detailed information about reversing Conficker.<br />
Its important to understand the overall behavior of the worm before tracing the code, because not all the code will be passed on every execution (there are some conditional checks before running other functionalities)<br />
Some variants work by using rundll32 as: rundll32.exe virus.dll,randomstring<br />
while other would need to play around the value of dwReason to continue the execution.<br />
Also watch out for the antidebug/anti VM codes.</p>
<p>AV companies usually have copies of this worm, so check your contacts.<br />
Or maybe you should try other malware source, like offensivecomputing or<br />
malwaredomainlist, etc.</p>
<p>Good luck.</p>
<p>-Rex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rex</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-275</link>
		<dc:creator>Rex</dc:creator>
		<pubDate>Thu, 23 Apr 2009 02:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-275</guid>
		<description>Hi John,

You can also check AV websites for detailed analysis of Conficker/Downadup variants. 
SRI also has very detailed information about reversing Conficker.
Its important to understand the overall behavior of the worm before tracing the code, because not all the code will be passed on every execution (there are some conditional checks before running other functionalities)
Some variants work by using rundll32 as: rundll32.exe virus.dll,
while other would need to play around the value of dwReason to continue the execution.
Also watch out for the antidebug/anti VM codes.

AV companies usually have copies of this worm, so check your contacts.
Or maybe you should try other malware source, like offensivecomputing or
malwaredomainlist, etc.

Good luck.

-Rex</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>You can also check AV websites for detailed analysis of Conficker/Downadup variants.<br />
SRI also has very detailed information about reversing Conficker.<br />
Its important to understand the overall behavior of the worm before tracing the code, because not all the code will be passed on every execution (there are some conditional checks before running other functionalities)<br />
Some variants work by using rundll32 as: rundll32.exe virus.dll,<br />
while other would need to play around the value of dwReason to continue the execution.<br />
Also watch out for the antidebug/anti VM codes.</p>
<p>AV companies usually have copies of this worm, so check your contacts.<br />
Or maybe you should try other malware source, like offensivecomputing or<br />
malwaredomainlist, etc.</p>
<p>Good luck.</p>
<p>-Rex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-263</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 20 Apr 2009 19:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-263</guid>
		<description>Hey Rex ,
Thanks for this artical,
I am doing a study on these Conficker A,B,C,D variants which is really creating problem now. My research is on Reverse Engineering these variants possibly  produce some prevention ideas. can you please tell me how to get infected in secured environment and where can I get these variants (A,B,C,D)   for my study and reverse eng. If you have any links related to these , please let me know.</description>
		<content:encoded><![CDATA[<p>Hey Rex ,<br />
Thanks for this artical,<br />
I am doing a study on these Conficker A,B,C,D variants which is really creating problem now. My research is on Reverse Engineering these variants possibly  produce some prevention ideas. can you please tell me how to get infected in secured environment and where can I get these variants (A,B,C,D)   for my study and reverse eng. If you have any links related to these , please let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: digitalpbk</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-225</link>
		<dc:creator>digitalpbk</dc:creator>
		<pubDate>Sun, 12 Apr 2009 07:03:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-225</guid>
		<description>Thank you for a good article,
how do we reverse engineer the code ?</description>
		<content:encoded><![CDATA[<p>Thank you for a good article,<br />
how do we reverse engineer the code ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 things to learn on March 28th</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-133</link>
		<dc:creator>10 things to learn on March 28th</dc:creator>
		<pubDate>Sat, 28 Mar 2009 03:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-133</guid>
		<description>[...] The art of unpacking Conficker worm &#124; Fortinet FortiGuard Blog Over the past two years, rarely did a worm get as much attention that Conficker (aka Downadup) is getting now. Its last variant, the infamous W32/Conficker.C, which surfaced in early March and is set to time-bomb on April 1, is literally all over the media. Of course, its features are well known and documented and some papers (such as SRI&#8217;s excellent analysis and a blog post from Sourcefire) even give interesting insights on the reverse engineering process. Indeed, while understanding the behavior of the malware is important to most people, learning how to understand it is even more important to some. [...]</description>
		<content:encoded><![CDATA[<p>[...] The art of unpacking Conficker worm | Fortinet FortiGuard Blog Over the past two years, rarely did a worm get as much attention that Conficker (aka Downadup) is getting now. Its last variant, the infamous W32/Conficker.C, which surfaced in early March and is set to time-bomb on April 1, is literally all over the media. Of course, its features are well known and documented and some papers (such as SRI&rsquo;s excellent analysis and a blog post from Sourcefire) even give interesting insights on the reverse engineering process. Indeed, while understanding the behavior of the malware is important to most people, learning how to understand it is even more important to some. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: March Threatscape Report: Virut, Conficker and social engineering &#124; Fortinet FortiGuard Blog</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-129</link>
		<dc:creator>March Threatscape Report: Virut, Conficker and social engineering &#124; Fortinet FortiGuard Blog</dc:creator>
		<pubDate>Fri, 27 Mar 2009 21:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-129</guid>
		<description>[...] simply becomes active on that date and will remain active afterwards. Given the amount of attention Conficker has received, it is likely the authors will attempt any sort of strike at a later date when it is less [...]</description>
		<content:encoded><![CDATA[<p>[...] simply becomes active on that date and will remain active afterwards. Given the amount of attention Conficker has received, it is likely the authors will attempt any sort of strike at a later date when it is less [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paulo Raponi</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-124</link>
		<dc:creator>Paulo Raponi</dc:creator>
		<pubDate>Fri, 27 Mar 2009 19:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-124</guid>
		<description>Great article! Congratulation Fortinet Team!


regards,

Paulo Raponi
FCNSA, FCNSP</description>
		<content:encoded><![CDATA[<p>Great article! Congratulation Fortinet Team!</p>
<p>regards,</p>
<p>Paulo Raponi<br />
FCNSA, FCNSP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: InformationSecurity</title>
		<link>http://blog.fortinet.com/the-art-of-unpacking-conficker-worm/comment-page-1/#comment-122</link>
		<dc:creator>InformationSecurity</dc:creator>
		<pubDate>Fri, 27 Mar 2009 07:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortinet.com/?p=216#comment-122</guid>
		<description>Thanks for sharing tips; we just tweeted this on Twitter under {Technical} category for readers interested in learning about reverse engineering in general (and Conficker, Downadup, Kido specifically). Keep up the good work. @SecurityQ</description>
		<content:encoded><![CDATA[<p>Thanks for sharing tips; we just tweeted this on Twitter under {Technical} category for readers interested in learning about reverse engineering in general (and Conficker, Downadup, Kido specifically). Keep up the good work. @SecurityQ</p>
]]></content:encoded>
	</item>
</channel>
</rss>
