« previous next »
Pages: [1]   Go Down

Author Topic: Avast didn't find Conficker.C  (Read 4198 times)

0 Members and 1 Guest are viewing this topic.

pakalolo2004

  • Guest
Avast didn't find Conficker.C
« on: November 18, 2009, 12:18:30 AM »
I have Avast V.4.8 (4.8.1356).  I'm curious about how does Microsoft Security Essentials (a free antivirus from Microsoft) can catch Conficker in my machine and Avast didn't?  I not sure why avast can't alert me or find conficker.  I'm not too sure about Avast.  I made sure my build is up to date and my virus definitions is up to date.  Infact, it downloads updates automatically.  If the support team reads this please inform me about this.  Thank you....
Logged

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37534
  • Not a avast user
Re: Avast didn't find Conficker.C
« Reply #1 on: November 18, 2009, 12:30:56 AM »
Logged

pakalolo2004

  • Guest
Re: Avast didn't find Conficker.C
« Reply #2 on: November 18, 2009, 12:35:47 AM »
Been there done that....did all the MS patch scan for it and it still comes back...but that wasn't my question....why didn't avast catch it?  why did Microsoft Security Essentials (MSSE) catch it instead?  MSE catches it when I plug in a USB drive.  It alerts me right away.  Avast didn't....why?
Logged

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37534
  • Not a avast user
Re: Avast didn't find Conficker.C
« Reply #3 on: November 18, 2009, 12:50:08 AM »
Quote
but that wasn't my question
well wasn't actually answering your question since i have no idea
When Avast have removal instruction on there web page i would think that also meant that Avast also would detect it? So  jepp strange
Logged

Offline superhacker

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 979
  • superhacker != super mario
Re:
« Reply #4 on: November 18, 2009, 01:03:37 AM »
its normal.when i plug my flash avast dont warn me but "autnrun disabled"and when i scan the disk avast catch it,may be avast should scan *.vmx files by default.
Logged
Dreams don't die, they just fall asleep.

Offline mathboyx215

  • Avast Evangelist
  • Poster
  • ***
  • Posts: 449
Re: Avast didn't find Conficker.C
« Reply #5 on: November 18, 2009, 02:16:44 AM »
Its not that avast can't catch but it is the fact that MSE caught it first.MSE probably scanned the usb first before avast did so thats probably why MSE detected it and avast didn't.Also, its not recommended to have 2 antivirus running together in real time.
Logged
It is not possible to divide anything by zero

Offline Yanto.Chiang

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1371
  • Soli Deo Gloria
    • PT Garuda Sinatriya Globalindo
Re: Avast didn't find Conficker.C
« Reply #6 on: November 18, 2009, 08:00:48 AM »
Hi There,

I agreed with mathboxy, avast actually could detect Win32:Config.
This happened with our customer many times, Once we plug our thumb drive to infected PC, and then play at our notebook with avast protection. Avast warned us about Win32:Config as autorun.inf, but if infected by rootkit you should need to do avast scan with your thumb drive.
Logged
Yanto Chiang | IT Security Consultants | AVAST Premium Security | GarudaSinatriya

Offline Milos

  • Avast team
  • Super Poster
  • *
  • Posts: 2294
Re: Avast didn't find Conficker.C
« Reply #7 on: November 19, 2009, 05:13:00 PM »
Hello,
send us (virus@avast.com) that sample to analyse, please. Use "Virus not detected" in subject.

Thank you,
Milos
Logged

Offline Maxx_original

  • Moderator
  • Super Poster
  • *
  • Posts: 1479
Re: Avast didn't find Conficker.C
« Reply #8 on: November 20, 2009, 10:15:48 AM »
it might be a MSE false positive or some corrupted file... i haven't seen a single undetected Conficker sample for quite a long time...
Logged
Pages: [1]   Go Up
« previous next »