Win32:Trojan-gen (other) in Breakaway Audio Enhancer

I have installed on my system “Breakaway for Windows Audio Enhancer” (version 1.01a) (http://www.claessonedwards.com/index.php) and had it installed for a year now. Never had any problems with it. A week ago, Avast started alerting me that there is a sample of Win32:Trojan-gen (other) in breakaway.exe which is the executable file of the Audio Enhancer. Since all of my audio goes through Breakaway, it’s quite annoying then when Avast kills it and with it all audio output.

Just wondering anyone else had this problems? There is a newer version of the Breakaway (1.20.12) available but that one seems to suffer from a number of bugs, so I’d rather stick with the older version.

Hi hallowed,

To be sure whether it is a false positive or not, please could you upload the file to www.virustotal.com and report back with the link to the results?


You could also send the file in a password protected archive to virus(at)avast(dot)com with ‘potential false positive’ in the subject line and the password in the email body.

or

You could add the file to the user files of the virus chest and send it from there:

Right click avast icon in taskbar -->click start avast antivirus -->right click scanner background → click virus chest → navigate to user files → click add files →
right click file -->email to alwil software.

NOTE:
The file will actually be uploaded when the next update is performed (you can do a manual update to initiate the sending)


You could also add a link to this thread and some more information when you do.

-Scott-

This is what the VirusTotal has to say about the setup file.

http://www.virustotal.com/analisis/ee8d8f10d36c6c0a629340592dea026c029ac8508e202adea29ac72646e94878-1252340889

And this is what it says about the program executable.

http://www.virustotal.com/analisis/4e9d8d8972226fc0d466391172b9f3f163682b9139f924a080316fc816d80226-1252341682

Well, I’m not too sure, it is enough for it to possibly not be a FP, but with mainly generic/heuristic detections, it may be a FP

We’ll have to see what the ALWIL team think about it. Have you sent the file to them?

-Edited-

Yes, I have sent it.

I guess it was a false positive after all. Avast is no longer reporting this as a threat.

Thank you, spg SCOTT, for the help and the advice. Cheers.

You’re welcome, glad that the issue is solved :slight_smile:

Welcome to the forums

-Scott-