clb123

Thank you ... things finally worked out.

I tried to register to access the HelpDesk, but the link in my verification email returns a HTTP 400 Bad Request. http://helpdesk.malwarebytes.org/verificat...ser/xxxxxxxxxx/ Is there a problem with verification URL I received?

I'm doing what I can to encourage anybody new to our threads to consider coming here instead of going full steam ahead with deleting what has been identified as the main file causing the problems. Hopefully we will get a "live one" for someone to work with to make sure that this gets added to the definitions.

OK ... it's holiday time now and folks are still struggling with this new one. Do I tell them to keep submitting them, or just keep deleting them and assume that Malwarebytes (and the other vendors) will catch up?

How long do new malware submissions take to be incorporated into MBAM? Not rushing them, or anything, but want to make sure that a file for for "wdmaud.sys" in "c:\windows" or "c:\windows\system32" made it to Malwarebytes the evening of December 28, or if it needs to be re-submitted. I would like to see users heading over here or another malware removal forum to take care of this instead of manually deleting the file(s) and still wondering what else they need to do. However, as long as the programs they are using aren't catching it, they are going to continue the self-cleaning process. I just hope they aren't leaving remnants of things that really need to still be removed. The thread started with someone who finally got rid of D:\WINDOWS\system32\sysaudio.sys (Rootkit.Agent) with Malwarebytes, but the thread morphed into one in which users were struggling with what turned out to be "wdmaud.sys" instead of (or in addition to) sysaudio.sys. http://www.google.com/support/forum/p/Web+...7c68d&hl=en

Never mind ... he has decided to not seek further assistance after reading the following thread at BleepingComputer: http://www.bleepingcomputer.com/forums/topic175838.html He is confident the discussion in the thread at BleepingComputer relates to what he had (rootkit.agent) ... and what MBAM identified and cleaned and that it is not a true rootkit issue.

I referred an individual to this forum after he ran Malwarebytes Anti-malware and it identified the following on his system: Backdoor.ProRat (stores in temp\pey125.tmp ) Rootkit.Agent (stores in Window\System\sysaudio.sys ) However, he has been unable to complete the registration process here (or at Bleeping Computer) in order to seek further assistance. He is not receiving the activation emails necessary to complete the registration. Is there something else he can do to gain access to this forum?