Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on August 22, 2014, 07:12:15 PM

Title: avast! failed to detect a threat while TrendMicro won...
Post by: REDACTED on August 22, 2014, 07:12:15 PM
avast! failed to detect a threat while TrendMicro won... see the attachment
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: TrueIndian on August 22, 2014, 07:17:33 PM
send the files to virus@avast.com via mail.

The files you are talking about are harmless.Its a gamurue worm payload.So if avast blocked the main worm autorun file and the executable.Thumbs.db is just harmless on its own.

Everyday 22,50000 or more pieces of viruses come out...no AV is 100% everything depends on your browsing habits and the way to work.Dont blame a AV.Every AV is statistically effective.It depends on which av protects A individual with bad browsing and no caution rather than B individual with the same AV and good habits.Always ask the person you are taking a USB from.Since you live in india alot of noob AV users are out there like quickheal and NPAV which are no better than crap.
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: Eddy on August 22, 2014, 07:18:00 PM
And your problem is.... ?

And where are the details?
What os/sp?
What exact version of avast?
What settings? (e.g. pup detection, scanning all files enabled or not)

There are also things avast detects while trend doesn't.
Same is true for any av.

Are you running multiple av's on the same system?
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: REDACTED on August 22, 2014, 07:20:46 PM
It may be harmless..but it hide all files in my pen drive...that is a harm to me..! After TM removed it my files returned
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: Pondus on August 22, 2014, 07:22:07 PM
Install MCShield.  www.mcshield.net
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: REDACTED on August 22, 2014, 07:22:38 PM
I'm using only avast...scanned my pendrive in another pc with TM
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: Pondus on August 22, 2014, 07:30:24 PM
Install MCS, plug in your pen drive and be surprised.   ;)

Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: REDACTED on August 24, 2014, 06:06:12 PM
Any compatibility problem between avast! and MCS ?
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: essexboy on August 24, 2014, 06:06:51 PM
None at all they are complimentary
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: REDACTED on August 24, 2014, 06:20:54 PM
Then ok..installing right now..thanks...
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: REDACTED on August 25, 2014, 05:46:40 PM
Pondus, here is the scan log..!! MCS found other threats which TM missed!. (What means  I:\autorun.inf > Suspicious > Renamed. (MD5: d41d8cd98f00b204e9800998ecf8427e) )
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: TrueIndian on August 26, 2014, 05:46:03 AM
Why dont you just send all the infected files to virus@avast.com.Just zip the files up and password protect them and mention the password in mail body..

It worthy job done rather than complaining here  ::)
Title: Re: avast! failed to detect a threat while TrendMicro won...
Post by: magna86 on August 26, 2014, 08:23:43 AM
@Harikrishnan
Quote
I:\autorun.inf > Suspicious > Renamed. (MD5: d41d8cd98f00b204e9800998ecf8427e

autorun.inf are just a trigger file, file that telling Windows to launch other executable file. In most cases, the executable file is some kind of installer.


Example:
(http://media.downloadblog.it/a/aut/autorun_02.gif)
This autorun.inf want to tell Windows to launch installer for Macromedia_Setup.exe



Open the detected autorun.inf (it is called now as autorun.inf.blocked) using notepad and see on witch file is targeting.
In any case, without some logs we can't tell you much.