"Tim Jackson" <> wrote in message
news: et...
> John D wrote:
>> "Tim Jackson" <> wrote in message
>> news:yc-dnYIInuYkH-...
>>> John D wrote:
>>>
>>>> I have been led to believe that the BIOS on a motherboad can be
>>>> attacked/infected but I have no knowledge of how one may check
>>>> and/or 'clean' same.
>>>>
>>> It can, but it isn't a likely attack route. The method varies
>>> according to the make and model of motherboard, and some boards have
>>> a jumper that must be set to allow any writing the flash ROM at all,
>>> or have a hard-coded alarm that warns you when writing is being
>>> enabled. So it is an unreliable and expensive method for a hacker.
>>>
>>> If you want to check, then look into your motherboard's flash update
>>> utility (probably on the CD that came with it, or on the
>>> manufacturer's website) and see if you can copy the existing flash
>>> contents. If so then you can make a baseline copy, and periodically
>>> repeat the process to make sure you continue to get the same data.
>>>
>>> You can probably find a security utility somewhere that will mirror
>>> the BIOS area of the memory map, which is pretty much the same thing
>>> in most cases
>>>
>>> And don't forget your tinfoil helmet to keep aliens from controlling
>>> your brain.
>>>
>>>
>>> Tim Jackson.
>>
>> I appreciate this information, Tim. Thank you for taking the time and
>> trouble to post.
>>
>> In another group, Shenan Stanley MVP said .........
>>
>> "If the 'gremlin' was in the BIOS - the only writable media I know
>> about that could act in the way you are implying internal to the
>> machine with your "somewhere on the motherboard" comment - you've
>> been more than infested with malware."
>>
>> Even whilst wearing my tinfoil helmet, my last PC was, I'm certain,
>> deliberately attacked - so there!
>>
>> --
>> John
>>
>>
>
Hi Tim - in line replies
> Deliberately attacked maybe, but actually compromised via the BIOS? I
> find that hard to believe. Although it is theoretically possible, it
> is pretty impracticable for the reasons I gave. I never heard reports
> of an attack "in the wild" that works that way. I'd agree with the
> MVP that this would be more than a simple infestation, and would look
> to physical security, I think you must have folded the tinfoil
> wrongly.
I thought I had been asking questions about such matters, not telling
you that *my* BIOS had been compromised! (Although I may have done it
myself - see later!).
> What were the characteristics of this malware, how did you identify
> it,
> does it have name, what symptoms did it cause, how did you cure it? I
> often find friends saying "my computer's got a virus" when actually
> they've got a memory defect or some such hardware fault. I'm sure
> readers here would be interested to hear technical details of such an
> attack.
How did I cure it? I scrapped the PC and bought another box - hand-built
by a mature student learning to be a computer technician at Exeter
college.
> I can't see why anyone would use such a method. If it was a personal
> attack on a single computer, then a pick-axe would probably be easier.
> If it was some sort of wild malware on the net it would have to be
> very specific to a particular type of motherboard, and why should
> someone want to take the time write that when there are much simpler
> ways to achieve their objectives.
The history is long and involved, but in the early part of 2006 I spent
hundreds of hours experimenting - including using my PC as a Honey-pot
(without any protection) and then opening up just about every file in
System32 with Notepad to read all manner of messages hidden in amongst
the gobbledegook! Instead of 'cleaning' I became quite adept at
flattening and reinstalling Windows from scratch (I have a retail copy
of XP Home and Microsoft disks - now for SP1, 2 and 3). I bought Norton
Internet Security 2006 and Ghost and spent many hours experimenting with
them too. I experimented with FDISK and used Darik's Boot and Nuke too.
http://en.wikipedia.org/wiki/Darik%27s_Boot_and_Nuke
I also downloaded - from what I thought/hoped was the bonio fido MSI
(Motherboard) web site - a copy of an updated BIOS and 'flashed' same. I
made and kept a 'BIOS Resue Disk' (Floppy). I'd like to email you a copy
of same to see if you consider it to have been 'the real McCoy'. There
is a text file called 'Copying' that begins ....
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
And ends like this .......
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type
`show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the
appropriate
parts of the General Public License. Of course, the commands you use
may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James
Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
************************
Might you have time to look? Please advise. Thanks.