Ad-aware detects namebench 1.0.5 as Win32.Toolbar.Softo (false positive)

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Download and run namebench with ad-aware installed and it throws a false
(hopefully) positive that labels the namebench.exe as "Win32.Toolbar.Softo
a malicious toolbar that may hijack a users browser and cause unwanted
advertisements and pop ups 

What is the expected output? What do you see instead?

To not have any detection occur.

What version of the product are you using? On what operating system?

Namebench 1.0.5 on Windows Vista using Ad-aware Free Anniversary Edition.

Please provide any additional information below.

Seems like a false positive, but it maybe be something you want to look
into because if a user hadn't read all the positive information about this
program, this false detection would have been an immediate reason to stop
using your program.

Original issue reported on code.google.com by pandu1...@gmail.com on 15 Dec 2009 at 5:37

[GoogleCodeExporter]

The Ad-Aware guys just pushed out a signature update - 0149.0115 - do you mind 
having Adware update it's definitions and then retrying?

Original comment by thomas.r...@gmail.com on 16 Dec 2009 at 8:50

• Changed title: Ad-aware detects namebench 1.0.5 as Win32.Toolbar.Softo (false positive)
• Changed state: Accepted

[GoogleCodeExporter]

Updated the definitions to 0149.0116 and ran namebench 1.0.5 and it still 
throws the
false positive.

Original comment by pandu1...@gmail.com on 16 Dec 2009 at 5:40

[GoogleCodeExporter]

1.1b1 also throws the false positive, though I am not sure yet of 1.1 final.

Original comment by tstromb...@google.com on 4 Jan 2010 at 10:38

• Changed state: Started

[GoogleCodeExporter]

I just submitted a vendor ticket with Ad-aware: 
http://www.lavasoft.com/support/securitycenter/vendor_inquiries.php

"Your vendor inquiry has been successfully sent. We will process your report as 
soon as 
possible."

Original comment by tstromb...@google.com on 4 Jan 2010 at 10:42

[GoogleCodeExporter]

Hi Thomas,

Thanks for your message. The application has been re-analysed and was not found 
to
display any malicious behaviour. The routine that detected the file in question 
has
been amended and as of the most recent update (0149.0126) this file is no longer
detected. Apologies for any inconvenience caused.

Regards,

Andy

Original comment by tstromb...@google.com on 5 Jan 2010 at 1:36

• Changed state: Fixed