On Nov 7, 8:25 pm, "David H. Lipman"
wrote:
> From: "maineearle"
>
> > Windows 7
>
> You didn't answer if "all partitions are NTFS" but I'll presume - yes.
>
> Since it uses NTFS there is no chance of a Boot Sector Infector like the "NYB" or "Form"
> virus and boot scan are not needed.
>
> I haven't heard that a boot scan can prevent or clean the TDL3 when it injects code into
> the MBR.
>
> --
> Dave
> Multi-AV Scanning Tool -http://multi-av.thespykiller.co.ukhttp://www.pctipp.ch/downloads/dl/35905.asp
There should be something in Windows--this is a proposal not a
statement that this exists--that will tell you if the MBR has
changed,by comparison with a hash to a previous version.
Also, it is interesting that the TDL rootkit will not run in a Virtual
Machine. But I've read somewhere that running on Windows 7 the XP
virtual machine (by VWware, the free version) can in theory infect
your real machine (since a XP VM can cross-over into your real non-
virtual machine).
Is it possible to run a Windows 7 virtual machine while running
Windows 7 OS? What advantage would that have? Perhaps to prevent
this rootkit.
RL
http://go.eset.com/us/resources/white-papers/TDL3-Analysis.pdf
Detecting virtual machine environment
The rootkit dropper checks whether the rootkit is being executed in
the context of a virtual
machine. It does so by reading the local descriptor table register
(LDTR) that is used to calculate the
linear address from the segment_selector:offset pair. Microsoft
Windows operating systems don’t use a
Local Descriptor Table (LDT), so the LDTR contains zero, but many
virtual machine programs use it,
nonetheless. In this way, the rootkit can easily check whether it is
running inside virtual machine. The
following figure shows how TDL3 uses this technique to ensure that it
isn’t executed inside a virtual
machine
>> Stay informed about: Microsoft Securiiy Essentials