Click here to get back home

I've done both of these 'silly things'!

 HomeNewsGroups | Search | About
 microsoft.public.security.virus    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
I've done both of these 'silly things'! ~BD~ 03-30-2008
Posted by ~BD~ on March 30, 2008, 5:07 pm
Please log in for more thread options

>
<snip>
> The virus could reside in the boot code, which 'format' wouldn't touch.
> You would effectively lose all data stored as files, while format went
> about its business sprucing up the underlying structure. Kind of like
> tightening up bookshelves to make them ready for some new books.
> The boot code isn't stored in a file, so is unaffected by formatting.
>
Thank you for your response. I'm beginning to understand! :)

Have you any idea how one may remove a virus from the boot code? TIA.



Posted by FromTheRafters on March 30, 2008, 5:48 pm
Please log in for more thread options

>
>>
> <snip>
>> The virus could reside in the boot code, which 'format' wouldn't touch.
>> You would effectively lose all data stored as files, while format went
>> about its business sprucing up the underlying structure. Kind of like
>> tightening up bookshelves to make them ready for some new books.
>> The boot code isn't stored in a file, so is unaffected by formatting.
>>
> Thank you for your response. I'm beginning to understand! :)
>
> Have you any idea how one may remove a virus from the boot code? TIA.

Sure, you overwrite/replace the correct code where it belongs. The trouble
is that sometimes you need part of the malicious code to recover your data
from the malware. Say for instance the virus encrypted some of your files,
and
you decide to overwrite the boot code (stomping on the virus) then reboot
only
to find the algorithm and 'key' to recovering your data was also stomped on.

..also consider that some of your backups may have been affected if the
malware
was there long enough.

The whole Fdisk/MBR thing just illustrates the old saw 'a little knowledge
is a dangerous thing'.



Posted by ~BD~ on March 30, 2008, 6:26 pm
Please log in for more thread options

>
>> <snip>
>> Have you any idea how one may remove a virus from the boot code? TIA.
>
> Sure, you overwrite/replace the correct code where it belongs. The trouble
> is that sometimes you need part of the malicious code to recover your data
> from the malware. Say for instance the virus encrypted some of your files,
> and
> you decide to overwrite the boot code (stomping on the virus) then reboot
> only
> to find the algorithm and 'key' to recovering your data was also stomped
> on.
>
> ..also consider that some of your backups may have been affected if the
> malware
> was there long enough.
>
> The whole Fdisk/MBR thing just illustrates the old saw 'a little knowledge
> is a dangerous thing'.
>
Thanks once again. You say "Sure, you overwrite/replace the correct code
where it belongs". You didn't explain *How*. If you know, please advise. TIA

Data retention is not relevant to this exercise. The object is to have a
'clean sheet' so to speak! :)
I do take on board, though, your point regarding backups possibly being
contaminated.



Posted by FromTheRafters on March 31, 2008, 4:43 pm
Please log in for more thread options

>
>>
>>> <snip>
>>> Have you any idea how one may remove a virus from the boot code? TIA.
>>
>> Sure, you overwrite/replace the correct code where it belongs. The
>> trouble
>> is that sometimes you need part of the malicious code to recover your
>> data
>> from the malware. Say for instance the virus encrypted some of your
>> files, and
>> you decide to overwrite the boot code (stomping on the virus) then reboot
>> only
>> to find the algorithm and 'key' to recovering your data was also stomped
>> on.
>>
>> ..also consider that some of your backups may have been affected if the
>> malware
>> was there long enough.
>>
>> The whole Fdisk/MBR thing just illustrates the old saw 'a little
>> knowledge is a dangerous thing'.
>>
> Thanks once again. You say "Sure, you overwrite/replace the correct code
> where it belongs". You didn't explain *How*. If you know, please advise.
> TIA

http://support.microsoft.com/kb/69013

After reading this, you should see how it could be dangerous if the user
doesn't know what he or she is doing. I used to have a dual boot box
Linux/Win98 using 'grub' as the OS chooser. Fdisk/mbr would have
messed things up considerably on that box for instance.

> Data retention is not relevant to this exercise. The object is to have a
> 'clean sheet' so to speak! :)

I can't tell you how to do it correctly for your system, because I don't
know
what correct is for your system.

> I do take on board, though, your point regarding backups possibly being
> contaminated.

The chances of you having the specific kind of virus that attaches to boot
code is extremely small.

Formatting the drive will likely be sufficient for your purposes.


Posted by kurt wismer on March 31, 2008, 11:57 pm
Please log in for more thread options
FromTheRafters wrote:
[snip]
>> I do take on board, though, your point regarding backups possibly
>> being contaminated.
>
> The chances of you having the specific kind of virus that attaches to
> boot code is extremely small.

true for viruses, less true for malware in general... specifically,
there's mbr malware being deployed via drive-by downloads from
compromised websites as we speak... i believe you can get more
information by searching for the keyword "mebroot"...

--
"it's not the right time to be sober
now the idiots have taken over
spreading like a social cancer,
is there an answer?"

Similar ThreadsPosted
My cursor has taken over my computer, opening windows and doing things April 4, 2007, 10:47 am
Where is the list of things Windows Defender Addresses? August 16, 2007, 8:56 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap