Need help removing backdoor.tidserv

Symantec turned this up on my computer, but can't get rid of it. Can anyone help me remove it?

Thanks!

Welcome to BC.
Please download Malwarebytes Anti-Malware and save it to your desktop.

• Make sure you are connected to the Internet.
• Double-click on mbam-setup.exe to install the application.
• When the installation begins, follow the prompts and do not make any changes to default settings.
• When installation has finished, make sure you leave both of these checked:
  • Update Malwarebytes' Anti-Malware
  • Launch Malwarebytes' Anti-Malware
• Then click Finish.
• MBAM will automatically start and you will be asked to update the program before performing a scan. If an update is found, the program will automatically update itself. Press the OK button to close that box and continue. If you encounter any problems while downloading the updates, manually download them from here and just double-click on mbam-rules.exe to install.
• On the Scanner tab:
  • Make sure the "Perform Quick Scan" option is selected.
  • Then click on the Scan button.
• If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
• The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
• When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
• Click OK to close the message box and continue with the removal process.
• Back at the main Scanner screen, click on the Show Results button to see a list of any malware that was found.
• Make sure that everything is checked, and click Remove Selected.
• When removal is completed, a log report will open in Notepad.
• The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
• Copy and paste the contents of that report in your next reply and exit MBAM.

Note: If MBAM encounters a file that is difficult to remove, you may be asked to reboot your computer so it can proceed with the disinfection process. Regardless if prompted to restart the computer or not, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware. MBAM may make changes to your registry as part of its disinfection routine. If you're using other security programs that detect registry changes, they may alert you after scanning with MBAM. Please permit the program to allow the changes.

Here is the log:

*edit* - that wasn't right... hold on...

OK, here we are...

Malwarebytes' Anti-Malware 1.30
Database version: 1412
Windows 5.1.2600 Service Pack 3

11/19/2008 2:58:01 PM
mbam-log-2008-11-19 (14-58-01).txt

Scan type: Quick Scan
Objects scanned: 79785
Time elapsed: 15 minute(s), 58 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 1
Registry Values Infected: 0
Registry Data Items Infected: 9
Folders Infected: 1
Files Infected: 4

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
HKEY_CLASSES_ROOT\homeview (Trojan.DNSChanger) -> Quarantined and deleted successfully.

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{409f5cbf-69cd-4028-9c8e-a50c65a32186}\NameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{e1ccd3f4-bcb2-4600-9d4b-51532bbe3a59}\DhcpNameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{e1ccd3f4-bcb2-4600-9d4b-51532bbe3a59}\NameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{409f5cbf-69cd-4028-9c8e-a50c65a32186}\NameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{e1ccd3f4-bcb2-4600-9d4b-51532bbe3a59}\DhcpNameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{e1ccd3f4-bcb2-4600-9d4b-51532bbe3a59}\NameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{409f5cbf-69cd-4028-9c8e-a50c65a32186}\NameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{e1ccd3f4-bcb2-4600-9d4b-51532bbe3a59}\DhcpNameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{e1ccd3f4-bcb2-4600-9d4b-51532bbe3a59}\NameServer (Trojan.DNSChanger) -> Data: 85.255.112.110;85.255.112.172 -> Quarantined and deleted successfully.

Folders Infected:
C:\resycled (Trojan.DNSChanger) -> Quarantined and deleted successfully.

Files Infected:
C:\resycled\boot.com (Trojan.DNSChanger) -> Quarantined and deleted successfully.
C:\WINDOWS\Temp\tempo-0E7.tmp (Trojan.FakeAlert) -> Quarantined and deleted successfully.
C:\WINDOWS\Temp\tempo-9E7.tmp (Trojan.FakeAlert) -> Quarantined and deleted successfully.
C:\WINDOWS\Temp\tempo-FA9.tmp (Trojan.FakeAlert) -> Quarantined and deleted successfully.

Edited by malibu434343, 19 November 2008 - 07:09 PM.

Well, I hope you don't mind but I skipped ahead a little. By reading some other threads, I picked up on what the usual plan of action is. I followed up my quick scan with a full scan and another quick scan that both resulted in no infected files. I installed ATF and deleted all the temp files (including the tmp4a.tmp file that symantec was picking up and couldn't delete before).

All seems to be normal now.

Thanks for this great site and amazing service!