Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

.fsharproj continues to repopulate after removing with malwarebytes


  • This topic is locked This topic is locked
13 replies to this topic

#1 spe1901

spe1901

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 26 June 2011 - 08:14 PM

Ok, I don't have the redirect issue as others have stated with this trojan, but after finding this with malwarebytes, it will re-populate after removing.

This is the log from my last malwarebytes.

Malwarebytes' Anti-Malware 1.51.0.1200
www.malwarebytes.org

Database version: 6915

Windows 5.1.2600 Service Pack 3, v.3264
Internet Explorer 7.0.5730.13

6/26/2011 7:58:47 PM
mbam-log-2011-06-26 (19-58-47).txt

Scan type: Quick scan
Objects scanned: 170598
Time elapsed: 2 minute(s), 40 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

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

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

---------
I've also noticed a .tmp file in my C:\Documents and Settings\Administrator folder that continues to show up (xqlfdsaljk.tmp)

What should I do next to get this rooted out of my registry so it will leave.

I have used malwarebytes, ccleaner, Spybot, and a few others both in safemode and normal to eliminate this. What's next?

Again, I am not currently getting a redirect, but this continues to show up in a scan in malwarebytes.
This all started when I rebooted, and I had a number of .exe programs issue a "CLI.exe has encountered a problem and needs to close. We are sorry for the inconvenience" window.

I get the same with MOM.exe (both deal with my graphics card)

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,166 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:55 AM

Posted 26 June 2011 - 08:29 PM

Hello, I moved this down one forum to Am I Infected.

We need to disable Spybot S&D's "TeaTimer" if running
TeaTimer works by preventing ANY changes to the system. It will attempt to undo any fixes we run, because it blocks these fixes from running.

In order to safeguard your system from problems that can be brought on by a half finished fix, we need to disable TeaTimer. We can reenable it when we're done if you like.
  • Open SpyBot Search and Destroy by going to Start -> All Programs -> Spybot Search and Destroy -> Spybot Search and Destroy.
  • If prompted with a legal dialog, accept the warning.
  • Click Mode > Advanced Mode.
    Posted Image
  • You may be presented with a warning dialog. If so, click Yes
  • Click on Tools and then Resident
    Posted Image
  • Uncheck this checkbox: "Resident TeaTimer {protection of over-all system settings) active"
  • Close/Exit Spybot Search and Destroy



Please download GooredFix from one of the locations below and save it to your Desktop
Download Mirror #1
Download Mirror #2
  • Ensure all Firefox windows are closed.
  • To run the tool, double-click it (XP), or right-click and select Run As Administrator (Vista).
  • When prompted to run the scan, click Yes.
  • GooredFix will check for infections, and then a log will appear. Please post the contents of that log in your next reply (it can also be found on your desktop, called GooredFix.txt).



Rerun MBAM (MalwareBytes) like this:

Open MBAM in normal mode and click Update tab, select Check for Updates,when done
click Scanner tab,select Quick scan and scan (normal mode).
After scan click Remove Selected, Post new scan log and Reboot into normal mode.

Please ask any needed questions,post logs and Let us know how the PC is running now.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 26 June 2011 - 10:18 PM

Ok, completed both steps (first one made sense)

Here is the first log.

----------

GooredFix by jpshortstuff (03.07.10.1)
Log created at 21:23 on 26/06/2011 (Administrator)
Firefox version 5.0 (en-US)

========== GooredScan ==========


========== GooredLog ==========

C:\Program Files\Mozilla Firefox\extensions\
{972ce4c6-7e08-4474-a285-3208198ce6fd} [02:26 19/07/2009]
{CAFEEFAC-0016-0000-0014-ABCDEFFEDCBA} [20:20 02/08/2009]
{CAFEEFAC-0016-0000-0015-ABCDEFFEDCBA} [01:17 05/08/2009]
{CAFEEFAC-0016-0000-0017-ABCDEFFEDCBA} [00:02 05/12/2009]
{CAFEEFAC-0016-0000-0020-ABCDEFFEDCBA} [16:09 14/04/2010]
{CAFEEFAC-0016-0000-0021-ABCDEFFEDCBA} [19:49 15/08/2010]
{CAFEEFAC-0016-0000-0022-ABCDEFFEDCBA} [04:55 24/11/2010]

C:\Documents and Settings\Administrator\Application Data\Mozilla\Firefox\Profiles\wlsaorhs.default\extensions\
DTToolbar@toolbarnet.com [22:15 25/04/2011]

[HKEY_LOCAL_MACHINE\Software\Mozilla\Firefox\Extensions]
"wrc@avast.com"="C:\Program Files\AVAST Software\Avast\WebRep\FF" [02:33 24/05/2011]
"jqs@sun.com"="C:\Program Files\Java\jre6\lib\deploy\jqs\ff" [20:20 02/08/2009]

---------- Old Logs ----------
GooredFix[02.22.56_27-06-2011].txt
GooredFix[21.58.51_26-06-2011].txt

-=E.O.F=-

---------
Here is the Malwarebytes logs, (I did one before reboot, and after. (both came up the same)

Malwarebytes' Anti-Malware 1.51.0.1200
www.malwarebytes.org

Database version: 6956

Windows 5.1.2600 Service Pack 3, v.3264
Internet Explorer 7.0.5730.13

6/26/2011 10:08:15 PM
mbam-log-2011-06-26 (22-08-15).txt

Scan type: Quick scan
Objects scanned: 171209
Time elapsed: 2 minute(s), 29 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)
------------

Computer seems to be running fine, Now I have to figure out why MOM.exe still seems to have a start up (kernal32.dll) failure.
now that this is clean up I'm most likely going to do a uninstall with ATI software and reload to see if it takes.

Unless you have any other suggestions.

Thanks..

#4 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 26 June 2011 - 10:27 PM

Sorry,

But I still have the .tmp file I mentioned before still popping back up. Should I delete the reference in my registry (HKEY_CLASSES_ROOT\Software\Xqlfdsaljk\CLSID

is this file normal?

#5 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,166 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:55 AM

Posted 27 June 2011 - 10:39 AM

That does appear to be a malware file as I cannot find it anywhere. Alayas back up the registry first as if you remove something wrong the PC may not boot.
Go to Start Run and type: regedit
Click OK.
On the left side, click to highlight My Computer at the top.
Go up to File Export
Make sure in that window there is a tick next to "All" under Export Branch.
Leave the "Save As Type" as "Registration Files".
Under "Filename" put RegBackup.
Choose to save it to C:\
Click save and then go to File Exit.

Or you can download and use ERUNTwhich is an excellent free tool that allows you to to take a snapshot (backup) of your registry before making changes and restore it when needed.


Probably better to try these first.

Please download ATF Cleaner by Atribune & save it to your desktop. alternate download link
  • Close all open browsers before using, especially FireFox. <-Important!!!
  • Double-click ATF-Cleaner.exe to run the program.
  • Under Main "Select Files to Delete" choose: Select All.
  • Click the Empty Selected button.
  • If you use Firefox browser click Firefox at the top and choose: Select All
  • Click the Empty Selected button.
    If you would like to keep your saved passwords, please click No at the prompt.
  • If you use Opera browser click Opera at the top and choose: Select All
  • Click the Empty Selected button.
    If you would like to keep your saved passwords, please click No at the prompt.
  • Click Exit on the Main menu to close the program.
Notes: On Vista, "Windows Temp" is disabled. To empty Temp, ATF-Cleaner must be Run As Administrator.
The Prefetch cleaning feature has been disabled for Vista Users. Tabs for applications that are not installed are grayed out.



Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.5.5.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 2.3.2.2 of the tool.
  • Double-click on TDSSKiller.exe to run the tool for known TDSS variants.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • If TDSSKiller does not run, try renaming it.
  • To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to How to change the file extension.
  • Click the Start Scan button.
  • Do not use the computer during the scan
  • If the scan completes with nothing found, click Close to exit.
  • If malicious objects are found, they will show in the Scan results - Select action for found objects and offer three options.
  • Ensure Cure (default) is selected, then click Continue > Reboot now to finish the cleaning process.
  • A log file named TDSSKiller_version_date_time_log.txt (i.e. TDSSKiller.2.4.0.0_27.07.2010_09.o7.26_log.txt) will be created and saved to the root directory (usually Local Disk C:).
  • Copy and paste the contents of that file in your next reply.


If TDSSKiller does not run, try renaming it. To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to these[/color] instructions. [color=green]In some cases it may be necessary to redownload TDSSKiller and randomly rename it before downloading and saving to the computer.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#6 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 27 June 2011 - 10:54 PM

Did what you asked.

TDSSKiller.exe didn't find anything except something related to my disk emulator.

here is the report.

2011/06/27 22:42:13.0343 114160 TDSS rootkit removing tool 2.5.6.0 Jun 27 2011 15:22:52
2011/06/27 22:42:13.0812 114160 ================================================================================
2011/06/27 22:42:13.0812 114160 SystemInfo:
2011/06/27 22:42:13.0812 114160
2011/06/27 22:42:13.0812 114160 OS Version: 5.1.2600 ServicePack: 3.0
2011/06/27 22:42:13.0812 114160 Product type: Workstation
2011/06/27 22:42:13.0812 114160 ComputerName: -------
2011/06/27 22:42:13.0812 114160 UserName: Administrator
2011/06/27 22:42:13.0812 114160 Windows directory: C:\WINDOWS
2011/06/27 22:42:13.0812 114160 System windows directory: C:\WINDOWS
2011/06/27 22:42:13.0812 114160 Processor architecture: Intel x86
2011/06/27 22:42:13.0812 114160 Number of processors: 2
2011/06/27 22:42:13.0812 114160 Page size: 0x1000
2011/06/27 22:42:13.0812 114160 Boot type: Normal boot
2011/06/27 22:42:13.0812 114160 ================================================================================
2011/06/27 22:42:14.0671 114160 Initialize success
2011/06/27 22:42:21.0656 116232 ================================================================================
2011/06/27 22:42:21.0656 116232 Scan started
2011/06/27 22:42:21.0656 116232 Mode: Manual;
2011/06/27 22:42:21.0656 116232 ================================================================================
2011/06/27 22:42:22.0578 116232 A3AB (21af8e9c727c6d7643ad497268f55bf1) C:\WINDOWS\system32\DRIVERS\A3AB.sys
2011/06/27 22:42:23.0312 116232 Aavmker4 (3f6884eff406238d39aaa892218f1df7) C:\WINDOWS\system32\drivers\Aavmker4.sys
2011/06/27 22:42:25.0500 116232 ACPI (15634a4d4371423ad438b93ee0519cb8) C:\WINDOWS\system32\DRIVERS\ACPI.sys
2011/06/27 22:42:26.0250 116232 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\drivers\ACPIEC.sys
2011/06/27 22:42:27.0703 116232 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
2011/06/27 22:42:28.0453 116232 AFD (e5d9213212ed08dc5f985049f7c68c09) C:\WINDOWS\System32\drivers\afd.sys
2011/06/27 22:42:31.0359 116232 akshasp (3f9f42085ab5b6a55498a539c54575ab) C:\WINDOWS\system32\DRIVERS\akshasp.sys
2011/06/27 22:42:32.0109 116232 aksusb (d2b95315cc47f9230006fdbcba394d8d) C:\WINDOWS\system32\DRIVERS\aksusb.sys
2011/06/27 22:42:33.0593 116232 Ambfilt (f6af59d6eee5e1c304f7f73706ad11d8) C:\WINDOWS\system32\drivers\Ambfilt.sys
2011/06/27 22:42:35.0093 116232 AR5416 (fe077e5d226ff586835237ea3e06bdc9) C:\WINDOWS\system32\DRIVERS\athw.sys
2011/06/27 22:42:35.0843 116232 Arp1394 (135e26db492bf04084efcb0bb4ad3117) C:\WINDOWS\system32\DRIVERS\arp1394.sys
2011/06/27 22:42:38.0734 116232 aswMon2 (c2181ef6b54752273a0759a968c59279) C:\WINDOWS\system32\drivers\aswMon2.sys
2011/06/27 22:42:39.0468 116232 aswRdr (ac48bdd4cd5d44af33087c06d6e9511c) C:\WINDOWS\system32\drivers\aswRdr.sys
2011/06/27 22:42:40.0218 116232 aswSP (d6788e3211afa9951ed7a4d617f68a4f) C:\WINDOWS\system32\drivers\aswSP.sys
2011/06/27 22:42:40.0937 116232 aswTdi (4d100c45517809439c7b6dd98997fa00) C:\WINDOWS\system32\drivers\aswTdi.sys
2011/06/27 22:42:41.0687 116232 AsyncMac (0d4681f78a20b50d691a4f3c9f75eb41) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2011/06/27 22:42:42.0421 116232 atapi (335bb30ed68cf3dc0ee2bddb438b6a9b) C:\WINDOWS\system32\drivers\atapi_TM.sys
2011/06/27 22:42:44.0078 116232 ati2mtag (23f1a61ae7553d086ef264c72afc4e6a) C:\WINDOWS\system32\DRIVERS\ati2mtag.sys
2011/06/27 22:42:44.0890 116232 Atmarpc (ecf89e5bd58e3a3cc2e7db0f0d9f6c6c) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2011/06/27 22:42:45.0625 116232 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
2011/06/27 22:42:46.0359 116232 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
2011/06/27 22:42:47.0093 116232 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
2011/06/27 22:42:48.0546 116232 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
2011/06/27 22:42:49.0281 116232 Cdfs (b7b2efd695bb6e937eb3e5b5465b6f47) C:\WINDOWS\system32\drivers\Cdfs.sys
2011/06/27 22:42:50.0015 116232 Cdrom (1f29616b1fc4d66a988cf97531bcf729) C:\WINDOWS\system32\DRIVERS\cdrom.sys
2011/06/27 22:42:54.0359 116232 Disk (023712144c69e60fcb662cda2715bf16) C:\WINDOWS\system32\DRIVERS\disk.sys
2011/06/27 22:42:55.0078 116232 DLABOIOM (a14524d3f130a57163e0b3e057fc85d5) C:\WINDOWS\system32\DLA\DLABOIOM.SYS
2011/06/27 22:42:55.0828 116232 DLACDBHM (7581407a6a3c56860ae31e6e423fe824) C:\WINDOWS\system32\Drivers\DLACDBHM.SYS
2011/06/27 22:42:56.0515 116232 DLADResN (7c4cdf8a684b63d7482e0bf7440dc3b5) C:\WINDOWS\system32\DLA\DLADResN.SYS
2011/06/27 22:42:57.0234 116232 DLAIFS_M (97bca2aac06a9fea56615b4b15bdb9b8) C:\WINDOWS\system32\DLA\DLAIFS_M.SYS
2011/06/27 22:42:57.0953 116232 DLAOPIOM (be8d558cf749424f0de612813f7c6725) C:\WINDOWS\system32\DLA\DLAOPIOM.SYS
2011/06/27 22:42:58.0671 116232 DLAPoolM (7e5277cb45dc5e2a86af8ce093c7ef31) C:\WINDOWS\system32\DLA\DLAPoolM.SYS
2011/06/27 22:42:59.0406 116232 DLARTL_N (693dfd92d41a3d270053cd97834e4960) C:\WINDOWS\system32\Drivers\DLARTL_N.SYS
2011/06/27 22:43:00.0109 116232 DLAUDFAM (d886b6d02b51e5bd61b8a571a16d5ca2) C:\WINDOWS\system32\DLA\DLAUDFAM.SYS
2011/06/27 22:43:00.0828 116232 DLAUDF_M (2c0ecf7a9d5162d87c64e2ae868b5039) C:\WINDOWS\system32\DLA\DLAUDF_M.SYS
2011/06/27 22:43:01.0593 116232 dmboot (1e5c89a65465f6d9674898eb4989cb86) C:\WINDOWS\system32\drivers\dmboot.sys
2011/06/27 22:43:02.0343 116232 dmio (6cf151f832ec417ffaf68f20ed7d39fb) C:\WINDOWS\system32\drivers\dmio.sys
2011/06/27 22:43:03.0078 116232 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
2011/06/27 22:43:03.0812 116232 DMusic (c561840c22148f5affb659d547efdbb0) C:\WINDOWS\system32\drivers\DMusic.sys
2011/06/27 22:43:05.0265 116232 drmkaud (c13ee685aa1a8950146f7f968eb090bd) C:\WINDOWS\system32\drivers\drmkaud.sys
2011/06/27 22:43:06.0000 116232 DRVMCDB (73623d89faef4d1aa600edee8b490bc5) C:\WINDOWS\system32\Drivers\DRVMCDB.SYS
2011/06/27 22:43:06.0734 116232 DRVNDDM (2aeee1600d0f14ba535f90a1f4411b54) C:\WINDOWS\system32\Drivers\DRVNDDM.SYS
2011/06/27 22:43:07.0468 116232 Fastfat (f696cf49c72f50ea0c1038c2daa98a00) C:\WINDOWS\system32\drivers\Fastfat.sys
2011/06/27 22:43:08.0203 116232 Fdc (650fa0d37498f9e2b201a09dbca0b85b) C:\WINDOWS\system32\DRIVERS\fdc.sys
2011/06/27 22:43:08.0953 116232 Fips (74947fd2d6a9151c0bb9c72bdaf0e894) C:\WINDOWS\system32\drivers\Fips.sys
2011/06/27 22:43:09.0687 116232 Flpydisk (3b8607a2bf5aec3dab18cf3612c07c1d) C:\WINDOWS\system32\DRIVERS\flpydisk.sys
2011/06/27 22:43:10.0421 116232 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
2011/06/27 22:43:11.0156 116232 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2011/06/27 22:43:11.0250 116232 gdrv (c6e3105b8c68c35cc1eb26a00fd1a8c6) C:\WINDOWS\gdrv.sys
2011/06/27 22:43:11.0890 116232 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys
2011/06/27 22:43:12.0640 116232 Gpc (9479c26a5691ccea495e2438ef11c948) C:\WINDOWS\system32\DRIVERS\msgpc.sys
2011/06/27 22:43:13.0359 116232 GVTDrv (689a8eef2a2d62b28a0a578a6196531c) C:\WINDOWS\system32\Drivers\GVTDrv.sys
2011/06/27 22:43:14.0109 116232 Hardlock (d95554949082fd29a04d351b58396718) C:\WINDOWS\system32\drivers\hardlock.sys
2011/06/27 22:43:14.0843 116232 HDAudBus (3fcc124b6e08ee0e9351f717dd136939) C:\WINDOWS\system32\DRIVERS\HDAudBus.sys
2011/06/27 22:43:15.0562 116232 hidusb (5f845228561e9545edc6f9ebfa15d338) C:\WINDOWS\system32\DRIVERS\hidusb.sys
2011/06/27 22:43:17.0000 116232 HPZid412 (5faba4775d4c61e55ec669d643ffc71f) C:\WINDOWS\system32\DRIVERS\HPZid412.sys
2011/06/27 22:43:17.0703 116232 HPZipr12 (a3c43980ee1f1beac778b44ea65dbdd4) C:\WINDOWS\system32\DRIVERS\HPZipr12.sys
2011/06/27 22:43:18.0453 116232 HPZius12 (2906949bd4e206f2bb0dd1896ce9f66f) C:\WINDOWS\system32\DRIVERS\HPZius12.sys
2011/06/27 22:43:19.0171 116232 HTTP (681afd0f5d6a12be948181b11a7f80a6) C:\WINDOWS\system32\Drivers\HTTP.sys
2011/06/27 22:43:21.0296 116232 i8042prt (30abe7000df369d8b1c4174429260aad) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
2011/06/27 22:43:22.0015 116232 Imapi (e32bf30d20b5c162775f9a3451e87b67) C:\WINDOWS\system32\DRIVERS\imapi.sys
2011/06/27 22:43:23.0531 116232 IntcAzAudAddService (0c5a04f0ffaebc25ac815ee14441a8cb) C:\WINDOWS\system32\drivers\RtkHDAud.sys
2011/06/27 22:43:24.0968 116232 intelppm (b3731ca1bdb32f83c817263646c31c15) C:\WINDOWS\system32\DRIVERS\intelppm.sys
2011/06/27 22:43:25.0687 116232 Ip6Fw (ef9bb587e33c2c245b5b83e882501ff6) C:\WINDOWS\system32\DRIVERS\Ip6Fw.sys
2011/06/27 22:43:26.0406 116232 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2011/06/27 22:43:27.0109 116232 IpInIp (30aba7a3f81e4b76c963cd6caa23cb49) C:\WINDOWS\system32\DRIVERS\ipinip.sys
2011/06/27 22:43:27.0828 116232 IpNat (eeb5787bd1445c8dc592f40691781774) C:\WINDOWS\system32\DRIVERS\ipnat.sys
2011/06/27 22:43:28.0546 116232 IPSec (bfea19daff955239a16a80c3cdf64fbe) C:\WINDOWS\system32\DRIVERS\ipsec.sys
2011/06/27 22:43:29.0265 116232 IRENUM (64e28d94089cff1c3c77f02f99ffac3f) C:\WINDOWS\system32\DRIVERS\irenum.sys
2011/06/27 22:43:29.0968 116232 isapnp (81a40a1118265dfc09c036f7776ebcc0) C:\WINDOWS\system32\DRIVERS\isapnp.sys
2011/06/27 22:43:30.0687 116232 JRAID (b07084095f8c03aadb9811c9df14b5e4) C:\WINDOWS\system32\DRIVERS\jraid.sys
2011/06/27 22:43:31.0390 116232 JSWSCIMD (20e5e4d1c055f36d341d7cda92b99dc8) C:\WINDOWS\system32\DRIVERS\jswscimd.sys
2011/06/27 22:43:32.0125 116232 Kbdclass (4ff969b48f320f6ce0b07247069c4c22) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2011/06/27 22:43:32.0828 116232 kbdhid (0cded60b750cb5023e901f1fe4e15556) C:\WINDOWS\system32\DRIVERS\kbdhid.sys
2011/06/27 22:43:33.0562 116232 kmixer (55e8d7039254728e9f071118184ff53b) C:\WINDOWS\system32\drivers\kmixer.sys
2011/06/27 22:43:34.0296 116232 KSecDD (23ea4c1a4ca28fd766ed2d3a5beaee3f) C:\WINDOWS\system32\drivers\KSecDD.sys
2011/06/27 22:43:35.0765 116232 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
2011/06/27 22:43:36.0484 116232 Modem (add0bb36498e4da9b1b6a3e201b60a18) C:\WINDOWS\system32\drivers\Modem.sys
2011/06/27 22:43:37.0218 116232 Monfilt (9fa7207d1b1adead88ae8eed9cdbbaa5) C:\WINDOWS\system32\drivers\Monfilt.sys
2011/06/27 22:43:37.0921 116232 Mouclass (e70558b84cb0cb9c739cc48ead2a4323) C:\WINDOWS\system32\DRIVERS\mouclass.sys
2011/06/27 22:43:38.0656 116232 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
2011/06/27 22:43:39.0375 116232 MountMgr (07be8cafd246a7dfb7fd4a387e936e92) C:\WINDOWS\system32\drivers\MountMgr.sys
2011/06/27 22:43:40.0796 116232 MRxDAV (ac816eff53bca79369f0b8643165368c) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2011/06/27 22:43:41.0531 116232 MRxSmb (73484c0377fefa76a4ddd48112ec93a3) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2011/06/27 22:43:42.0250 116232 Msfs (4d563545581e72c477ab00741b119853) C:\WINDOWS\system32\drivers\Msfs.sys
2011/06/27 22:43:42.0984 116232 MSKSSRV (85736f804191cb420a31aca2a7f0674f) C:\WINDOWS\system32\drivers\MSKSSRV.sys
2011/06/27 22:43:43.0703 116232 MSPCLOCK (e943adb93d83c5cbc0ca3f53f53b48cc) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2011/06/27 22:43:44.0421 116232 MSPQM (f6a726b8832db1f88326b8be98b11981) C:\WINDOWS\system32\drivers\MSPQM.sys
2011/06/27 22:43:45.0156 116232 mssmbios (f41814fd8811b2ba2a43a79aa8cce82a) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2011/06/27 22:43:45.0875 116232 Mup (2bb00d68cc9fbda1ee3d9bab9e4fd620) C:\WINDOWS\system32\drivers\Mup.sys
2011/06/27 22:43:46.0593 116232 NDIS (d1b364f049eb84a883c8a45d3b92ff3b) C:\WINDOWS\system32\drivers\NDIS.sys
2011/06/27 22:43:47.0328 116232 NdisTapi (7d0d0f2bf199c2df0a9d1b01406168ac) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2011/06/27 22:43:48.0031 116232 Ndisuio (e8969046dc350ecd1e9209dfe341c170) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2011/06/27 22:43:48.0750 116232 NdisWan (266fded9836490ff227ad13e677ba4fb) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2011/06/27 22:43:49.0468 116232 NDProxy (5aa58d218431c79e36a4878f18414637) C:\WINDOWS\system32\drivers\NDProxy.sys
2011/06/27 22:43:50.0218 116232 NetBIOS (c70b403d8158e11bf0d43d5b153cbe6b) C:\WINDOWS\system32\DRIVERS\netbios.sys
2011/06/27 22:43:50.0953 116232 NetBT (c181e1f7a2a251b7af6352dcbd8457f3) C:\WINDOWS\system32\DRIVERS\netbt.sys
2011/06/27 22:43:51.0656 116232 NIC1394 (17d865dd3bc94ae76e1909aeaee55f22) C:\WINDOWS\system32\DRIVERS\nic1394.sys
2011/06/27 22:43:52.0375 116232 Npfs (20c123afc574abf76ba35d39c26ae6df) C:\WINDOWS\system32\drivers\Npfs.sys
2011/06/27 22:43:53.0109 116232 Ntfs (34a993d7e519364f5d548b5726917753) C:\WINDOWS\system32\drivers\Ntfs.sys
2011/06/27 22:43:53.0828 116232 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
2011/06/27 22:43:54.0562 116232 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2011/06/27 22:43:55.0281 116232 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2011/06/27 22:43:56.0000 116232 NwlnkIpx (6fd296f9a891c2ca812c0f90015ef55b) C:\WINDOWS\system32\DRIVERS\nwlnkipx.sys
2011/06/27 22:43:56.0718 116232 NwlnkNb (56d34a67c05e94e16377c60609741ff8) C:\WINDOWS\system32\DRIVERS\nwlnknb.sys
2011/06/27 22:43:57.0468 116232 NwlnkSpx (c0bb7d1615e1acbdc99757f6ceaf8cf0) C:\WINDOWS\system32\DRIVERS\nwlnkspx.sys
2011/06/27 22:43:58.0187 116232 NWRDR (6662b694f1b38273127b3640bc40a460) C:\WINDOWS\system32\DRIVERS\nwrdr.sys
2011/06/27 22:43:58.0906 116232 ohci1394 (3a4abe329fc67757bf95e1d6fe531800) C:\WINDOWS\system32\DRIVERS\ohci1394.sys
2011/06/27 22:43:59.0625 116232 Parport (10572a94d8978619ce4845fe8595c9a5) C:\WINDOWS\system32\DRIVERS\parport.sys
2011/06/27 22:44:00.0359 116232 PartMgr (67075da61516adedd710a9da6c6c8acb) C:\WINDOWS\system32\drivers\PartMgr.sys
2011/06/27 22:44:01.0078 116232 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
2011/06/27 22:44:01.0890 116232 PCI (f3cebed46dc3a7f1758745c1d1fa5fcf) C:\WINDOWS\system32\DRIVERS\pci.sys
2011/06/27 22:44:03.0328 116232 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
2011/06/27 22:44:04.0046 116232 Pcmcia (1ec157cb90d06455d67c007ada4973ac) C:\WINDOWS\system32\drivers\Pcmcia.sys
2011/06/27 22:44:09.0062 116232 PptpMiniport (87d6a848dc367056778168d40a6f1a70) C:\WINDOWS\system32\DRIVERS\raspptp.sys
2011/06/27 22:44:09.0796 116232 PSched (8dc29e493cce832784a60bf7c120f132) C:\WINDOWS\system32\DRIVERS\psched.sys
2011/06/27 22:44:10.0515 116232 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
2011/06/27 22:44:11.0234 116232 PxHelp20 (153d02480a0a2f45785522e814c634b6) C:\WINDOWS\system32\Drivers\PxHelp20.sys
2011/06/27 22:44:15.0468 116232 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
2011/06/27 22:44:16.0171 116232 Rasl2tp (dbc6aeda3111edaf60948fc063565006) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2011/06/27 22:44:16.0921 116232 RasPppoe (96467fc3e135f0b174b8978bd8ce69f9) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2011/06/27 22:44:17.0625 116232 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
2011/06/27 22:44:18.0343 116232 Rdbss (1116a775bfa71f2c13f3d420da455ff2) C:\WINDOWS\system32\DRIVERS\rdbss.sys
2011/06/27 22:44:19.0046 116232 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2011/06/27 22:44:19.0765 116232 rdpdr (9b7b9221177c83c7cbfd20b4b67f23dc) C:\WINDOWS\system32\DRIVERS\rdpdr.sys
2011/06/27 22:44:20.0500 116232 RDPWD (0cd1bda7f6848e4de4eed3d36874ffb5) C:\WINDOWS\system32\drivers\RDPWD.sys
2011/06/27 22:44:21.0218 116232 redbook (11540f52cbc8a4c97467579bbf7ffae2) C:\WINDOWS\system32\DRIVERS\redbook.sys
2011/06/27 22:44:21.0953 116232 RTLE8023xp (eeb84629064abcb6198864d25bf15b1a) C:\WINDOWS\system32\DRIVERS\Rtenicxp.sys
2011/06/27 22:44:22.0671 116232 serenum (de23787927cb72533d4869855e955329) C:\WINDOWS\system32\DRIVERS\serenum.sys
2011/06/27 22:44:23.0406 116232 Serial (471168d4b9adfd1f9e692f8779455188) C:\WINDOWS\system32\DRIVERS\serial.sys
2011/06/27 22:44:24.0140 116232 Sfloppy (dc495a349dfd94fbfe4cf0689ed647b2) C:\WINDOWS\system32\drivers\Sfloppy.sys
2011/06/27 22:44:26.0281 116232 splitter (e477a633ea2d387788879a30666e5998) C:\WINDOWS\system32\drivers\splitter.sys
2011/06/27 22:44:27.0031 116232 sptd (cdddec541bc3c96f91ecb48759673505) C:\WINDOWS\system32\Drivers\sptd.sys
2011/06/27 22:44:27.0031 116232 Suspicious file (NoAccess): C:\WINDOWS\system32\Drivers\sptd.sys. md5: cdddec541bc3c96f91ecb48759673505
2011/06/27 22:44:27.0046 116232 sptd - detected LockedFile.Multi.Generic (1)
2011/06/27 22:44:27.0765 116232 Srv (388a576b405fd4c8a4886aa872e8e0f1) C:\WINDOWS\system32\DRIVERS\srv.sys
2011/06/27 22:44:28.0484 116232 swenum (a5491f57e70167a10ed40e19d36edd13) C:\WINDOWS\system32\DRIVERS\swenum.sys
2011/06/27 22:44:29.0234 116232 swmidi (5f8ab2829c52609e03560725eaf167f9) C:\WINDOWS\system32\drivers\swmidi.sys
2011/06/27 22:44:32.0796 116232 sysaudio (feaee2df25f435c153756707321bbf46) C:\WINDOWS\system32\drivers\sysaudio.sys
2011/06/27 22:44:33.0515 116232 Tcpip (25fa97dffd06153b735bfb7ad359bc65) C:\WINDOWS\system32\DRIVERS\tcpip.sys
2011/06/27 22:44:34.0250 116232 TDPIPE (76afdfea26d4cb16e81fa32a22c34376) C:\WINDOWS\system32\drivers\TDPIPE.sys
2011/06/27 22:44:34.0968 116232 TDTCP (2fc82251c9e895aa48624ebe05e5774e) C:\WINDOWS\system32\drivers\TDTCP.sys
2011/06/27 22:44:35.0687 116232 TermDD (4e55b6f75ad92f13d6abbf8d767cbcec) C:\WINDOWS\system32\DRIVERS\termdd.sys
2011/06/27 22:44:37.0125 116232 Udfs (90374e55f93f2883377902cb9cbfc6db) C:\WINDOWS\system32\drivers\Udfs.sys
2011/06/27 22:44:38.0593 116232 Update (415c2a770f4b6932308f9de7b19b3139) C:\WINDOWS\system32\DRIVERS\update.sys
2011/06/27 22:44:39.0312 116232 USBAAPL (d4fb6ecc60a428564ba8768b0e23c0fc) C:\WINDOWS\system32\Drivers\usbaapl.sys
2011/06/27 22:44:40.0046 116232 usbccgp (9a0a8be756bd7a9bad4a3d0e9fa7bd79) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2011/06/27 22:44:40.0781 116232 usbehci (d37fee874b49d951f68e788d40d8c196) C:\WINDOWS\system32\DRIVERS\usbehci.sys
2011/06/27 22:44:41.0484 116232 usbhub (8167383fe00199108f63269c2b8a99e1) C:\WINDOWS\system32\DRIVERS\usbhub.sys
2011/06/27 22:44:42.0203 116232 usbprint (14caa438f4ebd12dbd43db0273bc0fdc) C:\WINDOWS\system32\DRIVERS\usbprint.sys
2011/06/27 22:44:42.0937 116232 usbscan (5be9c3f196c607aaa072ed660f9c0423) C:\WINDOWS\system32\DRIVERS\usbscan.sys
2011/06/27 22:44:43.0656 116232 USBSTOR (e3eef7ae5105a9f99b1807031edb4171) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2011/06/27 22:44:44.0375 116232 usbuhci (b02addb9a345cbae360a29b2865c36a1) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
2011/06/27 22:44:45.0093 116232 usb_rndisx (e1b926095c657d7dcf364e42bfe9623d) C:\WINDOWS\system32\DRIVERS\usb8023x.sys
2011/06/27 22:44:45.0828 116232 VgaSave (cc1f0dd100f577e9b029547fee285813) C:\WINDOWS\System32\drivers\vga.sys
2011/06/27 22:44:47.0234 116232 VolSnap (2abf037f9d447424b58d73706b55b762) C:\WINDOWS\system32\drivers\VolSnap.sys
2011/06/27 22:44:47.0953 116232 vusbbus (e40c43c2e46dd15219b217429e4838b9) C:\WINDOWS\system32\DRIVERS\vusbbus.sys
2011/06/27 22:44:48.0671 116232 Wanarp (8794191476e6b93161baaa136e309454) C:\WINDOWS\system32\DRIVERS\wanarp.sys
2011/06/27 22:44:50.0078 116232 wdmaud (cf66393a0b2e361503bf381ac013b34a) C:\WINDOWS\system32\drivers\wdmaud.sys
2011/06/27 22:44:50.0812 116232 WSIMD (43f767d59bfc25d8f4fc2eb42043ec1e) C:\WINDOWS\system32\DRIVERS\wsimd.sys
2011/06/27 22:44:51.0531 116232 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/06/27 22:44:52.0234 116232 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2011/06/27 22:44:52.0250 116232 MBR (0x1B8) (8f558eb6672622401da993e1e865c861) \Device\Harddisk0\DR0
2011/06/27 22:44:52.0390 116232 Boot (0x1200) (02f5ee76526e4b748663b1494c82f97e) \Device\Harddisk0\DR0\Partition0
2011/06/27 22:44:52.0406 116232 ================================================================================
2011/06/27 22:44:52.0406 116232 Scan finished
2011/06/27 22:44:52.0406 116232 ================================================================================
2011/06/27 22:44:52.0406 115744 Detected object count: 1
2011/06/27 22:44:52.0406 115744 Actual detected object count: 1
2011/06/27 22:48:46.0671 115744 LockedFile.Multi.Generic(sptd) - User select action: Skip

#7 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,166 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:55 AM

Posted 28 June 2011 - 10:03 AM

That's OK, how's MBAM?

Edited by boopme, 28 June 2011 - 10:03 AM.

How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#8 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 29 June 2011 - 11:38 PM

Just performed another scan... it is still there.

So somewhere, something is asking to bring it back.

#9 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,166 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:55 AM

Posted 30 June 2011 - 09:36 AM

We could just kill the file,but since the earlier "CLI.exe has encountered " situation. This can be a dangerous RBOT infection and should be verified.
As this is a relatively common legitimate process with a somewhat cryptic name, it is common for virus writers and spyware vendors to disguise their malware as the genuine ATI Catalyst Control Center.

We need a deeper look. Please go here....
Preparation Guide ,do steps 6 - 9.

Create a DDS log and post it in the new topic explained in step 9,which is here Virus, Trojan, Spyware, and Malware Removal Logs and not in this topic,thanks.
If Gmer won't run,skip it and move on.
Let me know if that went well.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#10 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 01 July 2011 - 10:31 PM

I will most likely get back to this on the 4th or 5th.
I will let you know what I see.

Thanks.

#11 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 08 July 2011 - 11:38 PM

I can't even run the dds.scr. When I click it, it goes to Notepad and supplies a bunch of symbols and weird text. Example : M‰M3ҊQNUM

Sorry it took awhile to get to this, I had to also Uninstall Avast, seems that when I wanted to turn off scripts, it was asking for a password. I don't have a password listed for that. So I went into safe-mode and uninstalled.

#12 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,166 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:55 AM

Posted 09 July 2011 - 10:01 AM

opens in Notepad

please download this file: xp_scr_fix.

Unpack the file onto your desktop and double-click it. You will be asked if you wish to merge the file with you registry, say yes.

You should then be able to run DDS.scr.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#13 spe1901

spe1901
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:12:55 AM

Posted 09 July 2011 - 01:34 PM

Ok,

I ran the dds.scr and the gmer.exe.

I posted in the location you asked, I used the same title "fsharproj continues ....."

Let me know if you see anything that just sticks out like a sore thumb.

#14 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,166 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:55 AM

Posted 09 July 2011 - 10:49 PM

Ok,that post looks good.

Now that your log is properly posted, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a Malware Removal Team member, nor should you continue to ask for help elsewhere. Doing so can result in system changes which may not show it the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the Malware Removal Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the Malware Removal Team members are very busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the Malware Removal Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MRL Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users