<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Windows Enterprise Desktop &#187; eSage TDSS rootkit remover</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/tag/esage-tdss-rootkit-remover/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 13:11:52 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Beware the TDSS Rootkit Removal Tool!!!</title>
		<link>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/beware-the-tdss-rootkit-removal-tool/</link>
		<comments>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/beware-the-tdss-rootkit-removal-tool/#comments</comments>
		<pubDate>Wed, 12 May 2010 15:16:01 +0000</pubDate>
		<dc:creator>Ed Tittel</dc:creator>
				<category><![CDATA[be careful when using TDSS rootkit cleanup tool]]></category>
		<category><![CDATA[eSage TDSS rootkit remover]]></category>
		<category><![CDATA[TDSS rootkit remover clobbers Windows license key and activation info]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/?p=850</guid>
		<description><![CDATA[In the latest (May 2010) issue of Virus Bulletin, I read Alisa Shevchencko&#8217;s story &#8220;TDSS Infections &#8211; Quarterly Report&#8221; with some interest and a lively appreciation of the TDSS rootkit malware and infections over the past year. Upon learning that a detection and repair tool for this rootkit (which is extraordinarily difficult to detect, even [...]]]></description>
				<content:encoded><![CDATA[<p>In the latest (May 2010) issue of <a href="http://www.virusbtn.com/index" target="_blank">Virus Bulletin</a>, I read Alisa Shevchencko&#8217;s story &#8220;TDSS Infections &#8211; Quarterly Report&#8221; with some interest and a lively appreciation of the TDSS rootkit malware and infections over the past year. Upon learning that a detection and repair tool for this rootkit (which is extraordinarily difficult to detect, even for rootkit-specific tools) was available from Shevchenko&#8217;s employers Website (<a href="http://www.esagelab.com/files/tdss_remover_latest.rar" target="_blank">eSage Lab</a>) I decided to give it a shot. This program, simply called remover.exe scans systems to look for hidden driver files so that its users can remove them if and when they&#8217;re found. This tool comes with an undocumented catch, however, as I learned by electing to remove two hidden items that the program discovered on my system.</p>
<p>If you&#8217;re lucky, when you run this tool on your system, you&#8217;ll get a display that looks like this:</p>
<div id="attachment_849" class="wp-caption alignnone" style="width: 601px"><a href="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/79/files/2010/05/tdss-remover.jpg"><img class="size-medium wp-image-849" src="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/79/files/2010/05/tdss-remover.jpg" alt="The best outcome is when no hidden driver files are detected" width="591" height="417" /></a><p class="wp-caption-text">The best outcome is when no hidden driver files are detected</p></div>
<p>Alas, it turned out that the two hidden items that this program found on my system were hidden by Microsoft, not by any rootkit. When I removed them, I was removing my Windows 7 license key and activation data, so that when I rebooted my machine after the fix, I got the &#8220;black screen&#8221; background and a warning that my copy of Windows was not genuine. This was easy to fix, simply by re-entering my (valid) license key, and then re-activating Windows, but it did come as something of a surprise.</p>
<p>The two items that the progam discovered were:</p>
<ul>
<li>C:\Windows\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0</li>
<li>C:\Windows\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0</li>
</ul>
<p>Should you decide to run this program and it discovers exactly two hidden drivers, but no other signs of infection, you may want to check to make sure they don&#8217;t match this information. On the other hand, the fix is pretty easy if you do trash them and lose your license status and info, so you can go either way in deciding whether or not to allow the program to delete these questionable but benign items.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/beware-the-tdss-rootkit-removal-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
