Avast Doesn't Block XP Defender malware (ave.exe)
in [Spyware]
|
From: Dustin Cook on 3 Apr 2010 22:29 "The Real Truth MVP" <trt(a)void.com> wrote in news:hp8tec$3pl$1(a)leythos.motzarella.org: > And 1 year later the logo's are still there. Like I said dipshit they > contacted my attorney and I gave them my real name. They confirmed it. > The Truth hurts you so bad you can't stand it. One word... Liar. :) They were never able to confirm anything; as you couldn't get the MVP award based on your performance and the fact you have to be nominated by your peers; and you have none.... lol. -- "Hrrngh! Someday I'm going to hurl this...er...roll this...hrrngh.. nudge this boulder right down a cliff." - Goblin Warrior
From: David Kaye on 4 Apr 2010 00:37 ~BD~ <BoaterDave(a)hotmail.co.uk> wrote: >The Real Truth MVP wrote: >> Yes, all kidding aside it could be a new variant and he also only posted >> the program version number not virus definition version which is 100403-1 >> >> > >Maybe he'll check if he reads my reply to you! I did and I checked and it's 100403-1. I let Avast automatically update both the program and the definition files. It looks like this may be a trend. I walked a customer through a registry rollback (luckily the malware didn't take over safe mode) and had her set it back 3 days. Again, like me, she has Avast on her computer, and likely has the current definition file. I know she has the same program version I do. Funny thing is that in quick scan mode, MBam didn't see anything at all. On my computer it saw ave.exe. Thank goodness it was merely a matter of rolling back the registry and not something more serious like boot sector injections, etc. Still, she still has the malware on her computer; it's just the registry doen't know about it. Next time I visit her I'll have to check and get rid of it.
From: David Kaye on 4 Apr 2010 00:40 "gufus" <stop.nospam.gbbsg(a)shaw.ca> wrote: > >BTW, check your setup, your clock is wrong. For the 4th or 5th time, my clock is perfectly fine. It's the clock on my news server at Eternal September. Presently my clock says 8:40::03pm; that's Pacific Daylight Time.
From: David Kaye on 4 Apr 2010 00:46 ~BD~ <BoaterDave(a)hotmail.co.uk> wrote: >Maybe David Kaye has not used the very latest virus *update*. I don't >know, but something is odd if TRT's Avast! does catch the rogue file yet >David's doesn't! You guys are unbelievable. Once again, for the 3rd or is it the 4th time, both the Avast program and the definition file are as current as current can be, and Avast is also set to install both program and definition updates automatically. The FACT is that a version of ave.exe managed to get into my main computer, bypassing Avast entirely. Not only that but as an exe, ave.exe managed to download and install without Windows being the wiser, either. I can understand a Java or a VB script or some piece of code in Acrobat sneaking in, but this was an exe! The first I heard about it was when Windows warned me that the firewall had been turned off.
From: Beauregard T. Shagnasty on 3 Apr 2010 23:54
David Kaye wrote: > Date: Sun, 04 Apr 2010 04:40:04 GMT > Injection-Date: Sun, 4 Apr 2010 03:40:04 +0000 (UTC) > "gufus" <stop.nospam.gbbsg(a)shaw.ca> wrote: > >> BTW, check your setup, your clock is wrong. > > For the 4th or 5th time, my clock is perfectly fine. It's the clock > on my news server at Eternal September. > > Presently my clock says 8:40::03pm; that's Pacific Daylight Time. Let's see .. I'm using eternal-september as well. What's mine say? -- -bts -Four wheels carry the body; two wheels move the soul |