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

Some SSDT hooks driving me insane


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

#1 Kenny Brb

Kenny Brb

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 17 June 2009 - 07:12 PM

Hello!

First off, I apologize if i picked a wrong forum about the issue but it felt relevant.

Couple of days ago after booting my PC, before I even had a chance of doing anything, I got a message box saying something like "Your world of warcraft account has been updated.". Clicked OK resulted in game being started. Figured something is wrong there and I ran NOD32 full scan. It found some trojan (sadly i didn't write down its name so I cant be anymore specific about it) and removed it. Needless to say, I was rather worried about some trojans infesting my PC, even though i have antivirus up and running, so i decided to run couple of other antivirus programs just to make sure the problem is fixed. I've ran trial versions of Kaspersky, McAfee, AVG (maybe something else too which i fail to remember just now). Everything seemed fine, no threads found by any of those.

Today I have noticed windows auto update service is not running and when tried starting it, it said "invalid path". I've checked the service Path to executable and it has %fystemroom% in it. I've ran regedit and searched for "fystemroot". These were found in couple of places and I tried to replace them with %systemroot%. Setting new value of those keys failed (later on I understood they were marked as read only and all i had to do is set the key permissions). After browsing the net trying to understand the reason behind key value changing failure, somehow i came across RootRepeal.

Running RootRepeal is what made me totally lost. According to it there are 7 SSDT hooks active to stds.sys ( hooks to all kernel functions for reading/writing/enumerating registry). Unhook button seems to work but after scanning again they are back. File named stds.sys does not exist on my pc. Lurking the internet a bit more, made me believe that's some kind of rootkit and it's hidden for the OS (injected in MBR or so). I've tried rewriting the MBR with no success whatsoever. Not quite sure if it is intended but running fixmbr in recovery console warned me i have non standard MBR. Interestingly enough, running it second time (just after it has been reset) warned me exactly the same thing .. how can it be non standard immediately after writing the original one is beyond me, but thats not the point (i guess).

Another thing worth mentioning is that after first restart the hooks were still there, but this time the file wasn't called stds.sys but <some random 4 letters>.sys . The name changes after each restart.

Tried safe mode, removed all antivirus programs installed, even removed daemontools (according to some page it is vulnerable in some way to these 7 hooks exactly), nothing seems to work, the hooks just wont go away.

So here i am, having 7 hooks to <generate 4 letters>.sys , each antivirus, malware scanner I've ran do not detect anything. I am not even sure if it is not some windows "feature" at this point.

Please advice me how to proceed, I am totally lost :thumbsup:

EDIT: just realized I haven't written the functions being hooked
NtSetValueKey , NtQueryValueKey , NtQueryKey , NtOpenKey , NtEnumerateValueKey , NtEnumerateKey , NtCreateKey

Edited by Kenny Brb, 17 June 2009 - 07:15 PM.


BC AdBot (Login to Remove)

 


m

#2 Blade

Blade

    Strong in the Bleepforce


  • Site Admin
  • 12,701 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:08:37 PM

Posted 17 June 2009 - 07:21 PM

Hello Kenny Brb and :thumbsup: to Bleepingcomputer

First off, I feel like I should caution you that if you do not know exactly what you are doing, editing the registry manually is extremely dangerous, especially if you do not set a backup beforehand.

You have a rootkit on your system called TDSS. Rootkits are stealth components of many malware infections, they hide other malicious files from being seen by Windows, and thus any scanners we can run. To clean your system, we'll need to take out the rootkit first so we can see what we're really dealing with here.

Let's try and run Malwarebytes and see what it does; it can sometimes remove the rootkit you have on your system.

Please download Malwarebytes Anti-Malware and save it to your desktop.
alternate download link 1
alternate download link 2

IMPORTANT!!! - when you save the file, rename it to something random, such as bubbles.exe This must be done before beginning the download!

MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.
  • 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 definition 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. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
  • Exit MBAM when done.
Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.

***************************************************

If you have problems getting MBAM to execute after installation, navigate to the folder MBAM installed to and rename mbam.exe to bubbles.bat. Then double click on the file you just renamed to launch the program. Once MBAM is running, make sure you've updated it and then run a scan as directed above. Once the scan has completed, save the log somewhere you can easily find it, such as the desktop, and reboot the computer. Then, run another scan, and please submit the logs from both scans here for my review.

In your next reply, please include the following:
Two Malwarebytes logs

Edited by Blade Zephon, 17 June 2009 - 07:28 PM.

Posted Image

If I am helping you, it has been 48 hours since your last post, and I have yet to reply to your topic, please send me a PM
Become a BleepingComputer fan: Facebook
Follow us on Twitter!
Circle us on Google+


#3 Kenny Brb

Kenny Brb
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 17 June 2009 - 07:38 PM

Thank you for your swift response!

Malwarebytes was one of the scanners I have already ran but i uninstalled it and followed your instructions ( saving the download file to different name etc ) and ran it again. Not much luck again it seems.

Malwarebytes' Anti-Malware 1.38
Database version: 2301
Windows 5.1.2600 Service Pack 3

18.6.2009 г. 03:35:15
mbam-log-2009-06-18 (03-35-15).txt

Scan type: Quick Scan
Objects scanned: 94508
Time elapsed: 5 minute(s), 11 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)

#4 Blade

Blade

    Strong in the Bleepforce


  • Site Admin
  • 12,701 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:08:37 PM

Posted 17 June 2009 - 07:45 PM

Hrm. . . alright. . . let's try a different scanner.


Please download ATF Cleaner by Atribune & save it to your desktop.
  • 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.
Note: On Vista, "Windows Temp" is disabled. To empty "Windows Temp" ATF-Cleaner must be "Run as an Administrator".

***************************************************

Please download and scan with SUPERAntiSpyware Free
  • Double-click SUPERAntiSypware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If it will not start, go to Start > All Prgrams > SUPERAntiSpyware and click on Alternate Start.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the "General and Startup" tab, and under Start-up Options, make sure "Start SUPERAntiSpyware when Windows starts" box is unchecked.
  • Click the "Scanning Control" tab, and under Scanner Options, make sure the following are checked (uncheck all others):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen and exit the program.
  • Do not run a scan just yet.
Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with SUPERAntiSpyware as follows:
  • Launch the program and back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan and click "Next".
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes" and reboot normally.
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
In your next reply, please include the following:
SUPERAntiSpyware log

Posted Image

If I am helping you, it has been 48 hours since your last post, and I have yet to reply to your topic, please send me a PM
Become a BleepingComputer fan: Facebook
Follow us on Twitter!
Circle us on Google+


#5 Kenny Brb

Kenny Brb
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 18 June 2009 - 05:40 AM

Sorry for taking that long to reply, but that scan sure took a while.

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 06/18/2009 at 07:59 AM

Application Version : 4.26.1004

Core Rules Database Version : 3945
Trace Rules Database Version: 1887

Scan type : Complete Scan
Total Scan Time : 03:33:34

Memory items scanned : 216
Memory threats detected : 0
Registry items scanned : 5722
Registry threats detected : 0
File items scanned : 104067
File threats detected : 0

#6 Blade

Blade

    Strong in the Bleepforce


  • Site Admin
  • 12,701 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:08:37 PM

Posted 18 June 2009 - 03:11 PM

Hello:

Well since neither of those scanners are picking up anything. . . :thumbsup:

Let's try to gather some more information.

Please post the RootRepeal log you mentioned.

Also, most antivirii keep a record of scan logs. See if you can find the NOD32 log that came back with that trojan, and post it here.

Also also, I would check on your WoW account ASAP (use a different computer if you can, I'm not sure yours is secure yet); it sounds as though your login may have been compromised. If this is the case, you can contact Blizzard and they should be able to help you regain control.

~Blade

Edited by Blade Zephon, 18 June 2009 - 03:12 PM.

Posted Image

If I am helping you, it has been 48 hours since your last post, and I have yet to reply to your topic, please send me a PM
Become a BleepingComputer fan: Facebook
Follow us on Twitter!
Circle us on Google+


#7 Kenny Brb

Kenny Brb
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 18 June 2009 - 05:42 PM

Hello again!

Exactly the fact all scanners i could think of seems to think my PC is fine while these hooks still persists is what bothers me the most. I haven't really log to my wow account in several weeks so i am not bothered about it, for now I just want to figure out whether windows reinstall is in order ( that'd really suck though, my notebook doesn't have official support for xp and i despise vista so I'll have some fun times, again, looking for drivers ).

Here's the RootRepeal log:
Note: the hooked by "<unknown>" functions seems to be NOD, uninstalling it removes them. The spkx.sys ones however are permanent.

Cheers.

ROOTREPEAL © AD, 2007-2009
==================================================
Scan Time: 2009/06/19 01:29
Program Version: Version 1.3.0.0
Windows Version: Windows XP SP3
==================================================

Drivers
-------------------
Name: PCI_PNP5414
Image Path: \Driver\PCI_PNP5414
Address: 0x00000000 Size: 0 File Visible: No Signed: -
Status: -

Name: rootrepeal.sys
Image Path: C:\WINDOWS\system32\drivers\rootrepeal.sys
Address: 0xAAF74000 Size: 49152 File Visible: No Signed: -
Status: -

Name: spkx.sys
Image Path: spkx.sys
Address: 0xF7285000 Size: 1052672 File Visible: No Signed: -
Status: -

Name: sptd
Image Path: \Driver\sptd
Address: 0x00000000 Size: 0 File Visible: No Signed: -
Status: -

Hidden/Locked Files
-------------------
Path: C:\hiberfil.sys
Status: Locked to the Windows API!

Path: C:\WINDOWS\Prefetch\ROOTREPEAL.EXE-343E3165.pf
Status: Visible to the Windows API, but not on disk.

Path: c:\windows\temp\hlktmp
Status: Allocation size mismatch (API: 26181632, Raw: 0)

Path: c:\documents and settings\gbromov\application data\superantispyware.com\superantispyware\applogs\superantispyware-6-18-2009( 4-25-9 ).sdb
Status: Allocation size mismatch (API: 28672, Raw: 32768)

Path: C:\Documents and Settings\gbromov\Local Settings\Apps\2.0\C9VJMPBC.C8D\HK51N5QD.V0G\manifests\clickonce_bootstrap.exe.cdf-ms
Status: Locked to the Windows API!

Path: C:\Documents and Settings\gbromov\Local Settings\Apps\2.0\C9VJMPBC.C8D\HK51N5QD.V0G\manifests\clickonce_bootstrap.exe.manifest
Status: Locked to the Windows API!

SSDT
-------------------
#: 019 Function Name: NtAssignProcessToJobObject
Status: Hooked by "<unknown>" at address 0x89a56630

#: 041 Function Name: NtCreateKey
Status: Hooked by "spkx.sys" at address 0xf72860e0

#: 071 Function Name: NtEnumerateKey
Status: Hooked by "spkx.sys" at address 0xf72a4ca4

#: 073 Function Name: NtEnumerateValueKey
Status: Hooked by "spkx.sys" at address 0xf72a5032

#: 119 Function Name: NtOpenKey
Status: Hooked by "spkx.sys" at address 0xf72860c0

#: 122 Function Name: NtOpenProcess
Status: Hooked by "<unknown>" at address 0x89a55a60

#: 128 Function Name: NtOpenThread
Status: Hooked by "<unknown>" at address 0x89a55e80

#: 160 Function Name: NtQueryKey
Status: Hooked by "spkx.sys" at address 0xf72a510a

#: 177 Function Name: NtQueryValueKey
Status: Hooked by "spkx.sys" at address 0xf72a4f8a

#: 247 Function Name: NtSetValueKey
Status: Hooked by "spkx.sys" at address 0xf72a519c

#: 253 Function Name: NtSuspendProcess
Status: Hooked by "<unknown>" at address 0x89a56460

#: 254 Function Name: NtSuspendThread
Status: Hooked by "<unknown>" at address 0x89a56280

#: 257 Function Name: NtTerminateProcess
Status: Hooked by "<unknown>" at address 0x89a55c90

#: 258 Function Name: NtTerminateThread
Status: Hooked by "<unknown>" at address 0x89a560b0

Stealth Objects
-------------------
Object: Hidden Code [ETHREAD: 0x89ed3110]
Process: System Address: 0x89a54790 Size: 1000

Object: Hidden Code [Driver: Ntfs, IRP_MJ_CREATE]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_CLOSE]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_READ]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_WRITE]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_QUERY_INFORMATION]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_SET_INFORMATION]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_QUERY_EA]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_SET_EA]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_QUERY_VOLUME_INFORMATION]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_SET_VOLUME_INFORMATION]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_DIRECTORY_CONTROL]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_FILE_SYSTEM_CONTROL]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_SHUTDOWN]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_LOCK_CONTROL]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_CLEANUP]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_QUERY_SECURITY]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_SET_SECURITY]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_QUERY_QUOTA]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_SET_QUOTA]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Ntfs, IRP_MJ_PNP]
Process: System Address: 0x8a8801f8 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_CREATE]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_CLOSE]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_READ]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_WRITE]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_QUERY_INFORMATION]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_SET_INFORMATION]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_QUERY_EA]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_SET_EA]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_QUERY_VOLUME_INFORMATION]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_SET_VOLUME_INFORMATION]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_DIRECTORY_CONTROL]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_FILE_SYSTEM_CONTROL]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_SHUTDOWN]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_LOCK_CONTROL]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_CLEANUP]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Fastfat, IRP_MJ_PNP]
Process: System Address: 0x898ea500 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_CREATE]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_CLOSE]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_READ]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_WRITE]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_SHUTDOWN]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_POWER]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: Cdrom, IRP_MJ_PNP]
Process: System Address: 0x8a6351f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_CREATE]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_CLOSE]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_READ]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_WRITE]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_SHUTDOWN]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_POWER]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: dmio, IRP_MJ_PNP]
Process: System Address: 0x8a8f31f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_CREATE]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_CLOSE]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_POWER]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: usbohci, IRP_MJ_PNP]
Process: System Address: 0x8a67a1f8 Size: 121

Object: Hidden Code [Driver: Hard, IRP_MJ_CREATE]
Process: System Address: 0xe1d24a18 Size: 1512

Object: Hidden Code [Driver: Hard, IRP_MJ_CLOSE]
Process: System Address: 0xe1d24a18 Size: 1512

Object: Hidden Code [Driver: Hard, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0xe1d24a18 Size: 1512

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_CREATE]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_READ]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_WRITE]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_SHUTDOWN]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_CLEANUP]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_POWER]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: Ftdisk, IRP_MJ_PNP]
Process: System Address: 0x8a8821f8 Size: 121

Object: Hidden Code [Driver: prohlp02, IRP_MJ_CREATE]
Process: System Address: 0xe1000208 Size: 1276

Object: Hidden Code [Driver: prohlp02, IRP_MJ_CLOSE]
Process: System Address: 0xe1000208 Size: 1276

Object: Hidden Code [Driver: prohlp02, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0xe1000208 Size: 1276

Object: Hidden Code [Driver: NetBT, IRP_MJ_CREATE]
Process: System Address: 0x8a6a81f8 Size: 121

Object: Hidden Code [Driver: NetBT, IRP_MJ_CLOSE]
Process: System Address: 0x8a6a81f8 Size: 121

Object: Hidden Code [Driver: NetBT, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a6a81f8 Size: 121

Object: Hidden Code [Driver: NetBT, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a6a81f8 Size: 121

Object: Hidden Code [Driver: NetBT, IRP_MJ_CLEANUP]
Process: System Address: 0x8a6a81f8 Size: 121

Object: Hidden Code [Driver: NetBT, IRP_MJ_PNP]
Process: System Address: 0x8a6a81f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_CREATE]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_CLOSE]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_POWER]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: usbehci, IRP_MJ_PNP]
Process: System Address: 0x8a6421f8 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_CREATE]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_CREATE_NAMED_PIPE]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_CLOSE]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_READ]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_WRITE]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_QUERY_INFORMATION]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SET_INFORMATION]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_QUERY_EA]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SET_EA]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_QUERY_VOLUME_INFORMATION]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SET_VOLUME_INFORMATION]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_DIRECTORY_CONTROL]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_FILE_SYSTEM_CONTROL]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SHUTDOWN]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_LOCK_CONTROL]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_CLEANUP]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_CREATE_MAILSLOT]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_QUERY_SECURITY]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SET_SECURITY]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_POWER]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_DEVICE_CHANGE]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_QUERY_QUOTA]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_SET_QUOTA]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: MRxSmb, IRP_MJ_PNP]
Process: System Address: 0x8a5f0430 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_CREATE]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_CLOSE]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_READ]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_QUERY_INFORMATION]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_SET_INFORMATION]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_QUERY_VOLUME_INFORMATION]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_DIRECTORY_CONTROL]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_FILE_SYSTEM_CONTROL]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_SHUTDOWN]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_LOCK_CONTROL]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_CLEANUP]
Process: System Address: 0x897091f8 Size: 121

Object: Hidden Code [Driver: CdfsЅ扏煓Ёఄ䵃࢟գ, IRP_MJ_PNP]
Process: System Address: 0x897091f8 Size: 121

==EOF==

#8 Blade

Blade

    Strong in the Bleepforce


  • Site Admin
  • 12,701 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:08:37 PM

Posted 18 June 2009 - 06:42 PM

Alright. . . I'm an idiot. I misread your initial post, and topic title, as saying TDSS instead of SSDT. :thumbsup: That's what I get for being in a hurry, sorry.

Nevertheless, something with a randomly generated name is refusing to unhook itself; that screams malware to me. At this point you'll need help from the HJT Team over in the Malware Removal forum. I would like you to start a new thread HERE and include a link to this thread. Please make sure that you read the information about getting started before you start your thread.

It would be helpful if you post a note here once you have completed the steps in the guide and have started your topic in malware removal. Good luck and be patient. Help is on the way!

Posted Image

If I am helping you, it has been 48 hours since your last post, and I have yet to reply to your topic, please send me a PM
Become a BleepingComputer fan: Facebook
Follow us on Twitter!
Circle us on Google+


#9 Kenny Brb

Kenny Brb
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 18 June 2009 - 07:04 PM

Thank you again!

I've created a thread in the forum you mentioned, just wanted to post the link here if anyone happens to read the thread (having same issue or whatever) and curious how it is going.

http://www.bleepingcomputer.com/forums/t/234980/unknown-malware-problem-ssdt-hooks/

#10 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,713 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:08:37 PM

Posted 18 June 2009 - 08:43 PM

Hello,

Good. That was thoughtful of you. Now that you have posted a log, 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 HJT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in 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 HJT 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 HJT Team members are EXTREMELY 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 HJT 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 HJT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take a while (possibly a over a week, possibly less; it's hard to say) to get a response but your log will be reviewed and answered as soon as possible

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :thumbsup:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users