<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Malware IN Registry a.k.a If It Can&#8217;t Be Done, Why Am I Looking At It?</title>
	<atom:link href="http://www.cutawaysecurity.com/blog/archives/622/feed" rel="self" type="application/rss+xml" />
	<link>http://www.cutawaysecurity.com/blog/archives/622</link>
	<description>Cutaway's Observations, Opinions, Rants, Raves, Tantrums, and Tirades</description>
	<lastBuildDate>Wed, 02 Jun 2010 22:30:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MHL</title>
		<link>http://www.cutawaysecurity.com/blog/archives/622/comment-page-1#comment-31171</link>
		<dc:creator>MHL</dc:creator>
		<pubDate>Sun, 02 Aug 2009 01:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.cutawaysecurity.com/blog/?p=622#comment-31171</guid>
		<description>Hi Don, nice write up. The Clampi/Ligats trojan stores DLLs in the registry, but they&#039;re encrypted so its not so easy to identify by looking for MZ. Here&#039;s a reference if you&#039;re interested: http://mnin.blogspot.com/2008/11/locating-hidden-clampi-dlls-vad-style.html</description>
		<content:encoded><![CDATA[<p>Hi Don, nice write up. The Clampi/Ligats trojan stores DLLs in the registry, but they&#8217;re encrypted so its not so easy to identify by looking for MZ. Here&#8217;s a reference if you&#8217;re interested: <a href="http://mnin.blogspot.com/2008/11/locating-hidden-clampi-dlls-vad-style.html" rel="nofollow">http://mnin.blogspot.com/2008/11/locating-hidden-clampi-dlls-vad-style.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cutaway</title>
		<link>http://www.cutawaysecurity.com/blog/archives/622/comment-page-1#comment-31169</link>
		<dc:creator>cutaway</dc:creator>
		<pubDate>Wed, 29 Jul 2009 14:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.cutawaysecurity.com/blog/?p=622#comment-31169</guid>
		<description>@John,

   I don&#039;t think we have seen the last of the possibilities with the registry.  I do like to see people trying to think of the next things that can occur.  This helps us be proactive with our tool development.  As usual this is going to be a reaction game.  What I would really like to see Microsoft do is put out a good document on how to protect the registry.  Although I must admit I have not actively searched for one.  Looks like I have a new task.

Thank you,
Don</description>
		<content:encoded><![CDATA[<p>@John,</p>
<p>   I don&#8217;t think we have seen the last of the possibilities with the registry.  I do like to see people trying to think of the next things that can occur.  This helps us be proactive with our tool development.  As usual this is going to be a reaction game.  What I would really like to see Microsoft do is put out a good document on how to protect the registry.  Although I must admit I have not actively searched for one.  Looks like I have a new task.</p>
<p>Thank you,<br />
Don</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cutaway</title>
		<link>http://www.cutawaysecurity.com/blog/archives/622/comment-page-1#comment-31168</link>
		<dc:creator>cutaway</dc:creator>
		<pubDate>Wed, 29 Jul 2009 14:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.cutawaysecurity.com/blog/?p=622#comment-31168</guid>
		<description>@Stefan,

   I believe you are correct but have not verified.  I was not trying to single Symantec or Microsoft out.  This could be a size issue, or a system stability issue, I am not completely certain.  But that is why we write tools to assist AV.  More on this later.  

Thank you,
Don</description>
		<content:encoded><![CDATA[<p>@Stefan,</p>
<p>   I believe you are correct but have not verified.  I was not trying to single Symantec or Microsoft out.  This could be a size issue, or a system stability issue, I am not completely certain.  But that is why we write tools to assist AV.  More on this later.  </p>
<p>Thank you,<br />
Don</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://www.cutawaysecurity.com/blog/archives/622/comment-page-1#comment-31167</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Wed, 29 Jul 2009 12:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.cutawaysecurity.com/blog/?p=622#comment-31167</guid>
		<description>Please correct if I&#039;m wrong but wrt AV products &quot;not actively scan[ning] the whole registry looking for malicous behavior&quot; I&#039;m fairly sure that there currently isn&#039;t ANY AV vendor which does this.

Anyone?</description>
		<content:encoded><![CDATA[<p>Please correct if I&#8217;m wrong but wrt AV products &#8220;not actively scan[ning] the whole registry looking for malicous behavior&#8221; I&#8217;m fairly sure that there currently isn&#8217;t ANY AV vendor which does this.</p>
<p>Anyone?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting Information Security Bits for 07/28/2009 &#124; Infosec Ramblings</title>
		<link>http://www.cutawaysecurity.com/blog/archives/622/comment-page-1#comment-31164</link>
		<dc:creator>Interesting Information Security Bits for 07/28/2009 &#124; Infosec Ramblings</dc:creator>
		<pubDate>Tue, 28 Jul 2009 21:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.cutawaysecurity.com/blog/?p=622#comment-31164</guid>
		<description>[...] a couple other posts that are worth reading too. This is very cool&#8230;scary&#8230;but very cool. Security Ripcord &gt;&gt; Blog Archive &gt;&gt; Malware IN Registry a.k.a If It Can&#8217;t Be Done,... Tags: ( registry malware [...]</description>
		<content:encoded><![CDATA[<p>[...] a couple other posts that are worth reading too. This is very cool&#8230;scary&#8230;but very cool. Security Ripcord &gt;&gt; Blog Archive &gt;&gt; Malware IN Registry a.k.a If It Can&#8217;t Be Done,&#8230; Tags: ( registry malware [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John McCash</title>
		<link>http://www.cutawaysecurity.com/blog/archives/622/comment-page-1#comment-31163</link>
		<dc:creator>John McCash</dc:creator>
		<pubDate>Tue, 28 Jul 2009 16:15:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.cutawaysecurity.com/blog/?p=622#comment-31163</guid>
		<description>A coworker and I just had an interesting discussion about this... I take it in your case the malware in question was just writing itself from the registry to disk and then executing from there. However I suspect that if somebody could find a  flaw in a routine that reads data from the registry, (Say an unchecked string buffer? No of course not. That could never happen.) they could probably use it to bootstrap code out of the registry that wouldn&#039;t have to reside elsewhere on disk at all. A creepy thought, no?</description>
		<content:encoded><![CDATA[<p>A coworker and I just had an interesting discussion about this&#8230; I take it in your case the malware in question was just writing itself from the registry to disk and then executing from there. However I suspect that if somebody could find a  flaw in a routine that reads data from the registry, (Say an unchecked string buffer? No of course not. That could never happen.) they could probably use it to bootstrap code out of the registry that wouldn&#8217;t have to reside elsewhere on disk at all. A creepy thought, no?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
