moo.dll in mirc

[outboard]

hi i have just downloaded avast and love the look of it .. it was recommended to me by one of the sysops over at phreik chat <<<< unashamed plugging of chat server> the first scan i have done has found several copies of moo.dll and identified it as a warning-:
sign of "win32:irc [drp]"  has been found in "c:\...........\mirc ....\ moo\moo.dll" file

and the recommendation is to move it to the virus chest ...

as far as i understand this just returns motherboard and system info for use in mirc and is not a threat to security

am i wrong ?
will avast now forever show my status as infected ?
is there a way of reassuring avast that moo is harmless?
am i scanning too thoroughly ?

[oldman]

Hi, welcome to the forums!

Submit the file to virustotal, a multi  online scanner site. http://www.virustotal.com/xhtml/index_en.html

If avast is the only one detecting it, it probably is a false positve.

To prevent avast from detecting it during a scan, add the file to the exclution list. Right click the "a" icon, program settings, exclusion. Add the file. You can use the browse button.

Submit the file in a password protected zipped email to virus@avast.com. Include the password, why you think it is a fp, which version of avast and vps that detected the file.

If it's in the chest you will have to restore it before submitting it to virustotal.

HTH

[mauserme]

I feel a little silly asking, but what are the full paths of your moo.dll's?

If c:\programfiles\ ... then it might be OK and just confirm with Virus Total as oldman suggested.

If you find any instances in c:\windows ... or c:\windows\system32 ... I would be suspicious.

[outboard]

I feel a little silly asking, but what are the full paths of your moo.dll's?

If c:\programfiles\ ... then it might be OK and just confirm with Virus Total as oldman suggested.

If you find any instances in c:\windows ... or c:\windows\system32 ... I would be suspicious.

it is as you suggest c:\programfiles\.....\ (scriptname)\mirc\moo\moo.dll
i would be suitably concerned if mirc was writting files outside of its own folders
but thanks for the  reply