This past May, Webroot surveyed more than 600 IT decision-makers at medium-sized companies to see how these small businesses perceived new threats facing their organizations. Read what Webroot CISO, Gary Hayslip, has to say about the survey in part 1 of this 2-part blog series.
COURSE of the MONTH
8 days, 23 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Help reading GMER log - am I still infected
Posted on 2010-09-24
Hello,
I got whacked Monday with a fake Microsoft Security Essentials. While attempting to clean it I got hit with what Symantec calls "Boot.Tidserv" - little bugger infected my MBR - I removed it with TDSSKiller.exe from Kaspersky which is a stand alone tools created to clean this infection. Of course I had multiple spyware / viral problems - I used Malwarebytes, SuperAntispyware, and Spybot multiple times to clean up everything. Additionally I have run Panda's online scanner, Eset Online scanner, Blacklight and now GMER. Any infections that were detected I researched their damage and removed or fixed what I found... meaning added registry entries, directories etc..
I feel I'm at the final stage of clean up, however, I don't know how to interpret GMER's output / log. Below is the log after I ran GMER - would someone please take a look and tell me if it look like I'm NOT still infected by a rootkit. (Nothing came up in RED in GMER.)
Thank you
GMER LOG
GMER 1.0.15.15281 - http://www.gmer.net
Rootkit scan 2010-09-23 16:11:14
Windows 5.1.2600 Service Pack 3
Running: rj5xekhw.exe; Driver: C:\DOCUME~1\BSOBOC~1\LOCAL
---- System - GMER 1.0.15 ----
SSDT 8A670A68 ZwConnectPort
SSDT \??\C:\Program Files\Symantec\SYMEVENT.SY
SSDT \??\C:\Program Files\Symantec\SYMEVENT.SY
---- Kernel code sections - GMER 1.0.15 ----
.text C:\WINDOWS\system32\DRIVER
---- Devices - GMER 1.0.15 ----
AttachedDevice \FileSystem\Ntfs \Ntfs SYMEVENT.SYS (Symantec Event Library/Symantec Corporation)
AttachedDevice \Driver\Tcpip \Device\Ip SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\Tcpip \Device\Tcp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\Ftdisk \Device\HarddiskVolume1 snapman.sys (Acronis Snapshot API/Acronis)
AttachedDevice \Driver\Tcpip \Device\Udp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\Tcpip \Device\RawIp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
---- Registry - GMER 1.0.15 ----
Reg HKLM\SOFTWARE\Classes\CLSI
Reg HKLM\SOFTWARE\Classes\CLSI
---- EOF - GMER 1.0.15 ----
I got whacked Monday with a fake Microsoft Security Essentials. While attempting to clean it I got hit with what Symantec calls "Boot.Tidserv" - little bugger infected my MBR - I removed it with TDSSKiller.exe from Kaspersky which is a stand alone tools created to clean this infection. Of course I had multiple spyware / viral problems - I used Malwarebytes, SuperAntispyware, and Spybot multiple times to clean up everything. Additionally I have run Panda's online scanner, Eset Online scanner, Blacklight and now GMER. Any infections that were detected I researched their damage and removed or fixed what I found... meaning added registry entries, directories etc..
I feel I'm at the final stage of clean up, however, I don't know how to interpret GMER's output / log. Below is the log after I ran GMER - would someone please take a look and tell me if it look like I'm NOT still infected by a rootkit. (Nothing came up in RED in GMER.)
Thank you
GMER LOG
GMER 1.0.15.15281 - http://www.gmer.net
Rootkit scan 2010-09-23 16:11:14
Windows 5.1.2600 Service Pack 3
Running: rj5xekhw.exe; Driver: C:\DOCUME~1\BSOBOC~1\LOCAL
---- System - GMER 1.0.15 ----
SSDT 8A670A68 ZwConnectPort
SSDT \??\C:\Program Files\Symantec\SYMEVENT.SY
SSDT \??\C:\Program Files\Symantec\SYMEVENT.SY
---- Kernel code sections - GMER 1.0.15 ----
.text C:\WINDOWS\system32\DRIVER
---- Devices - GMER 1.0.15 ----
AttachedDevice \FileSystem\Ntfs \Ntfs SYMEVENT.SYS (Symantec Event Library/Symantec Corporation)
AttachedDevice \Driver\Tcpip \Device\Ip SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\Tcpip \Device\Tcp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\Ftdisk \Device\HarddiskVolume1 snapman.sys (Acronis Snapshot API/Acronis)
AttachedDevice \Driver\Tcpip \Device\Udp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\Tcpip \Device\RawIp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
---- Registry - GMER 1.0.15 ----
Reg HKLM\SOFTWARE\Classes\CLSI
Reg HKLM\SOFTWARE\Classes\CLSI
---- EOF - GMER 1.0.15 ----
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
-
2
- +1
7 Comments
Its impossible to tell from this log. Its not 'explicitly' stating there is a backdoor however those reg codes are gibberish to us. I would reommend check them out to make sure they are legit. However GMER is not stating that it found anything. Juding off this log file alone i would say there are not rootkits there w/o knowing whats in those reg keys.
Log looks ok.
Run this quick scanner to see if it detects anything outside of cookies.
Save Xml log if so
http://www.surfright.nl/en/hitmanpro
Run this quick scanner to see if it detects anything outside of cookies.
Save Xml log if so
http://www.surfright.nl/en/hitmanpro
Active 4 days ago
Bahpoopie,
Thanks - you are correct - those registry codes are looking like they came from the viral infection. I cannot take permission of the final key - I can however view it in GMER - as soon as I went to screw with it with GMER opened - whamo - my computer rebooted! Sorry for the "sparse" posting, I know it didn't give you a complete picture of what is going on with my pc. I'm going to look at a way to remove that registry key.
Again, I cannot take permission, I even tried in Safe Mode as the Administrator. I let you know how I make out.
Thanks
Thanks - you are correct - those registry codes are looking like they came from the viral infection. I cannot take permission of the final key - I can however view it in GMER - as soon as I went to screw with it with GMER opened - whamo - my computer rebooted! Sorry for the "sparse" posting, I know it didn't give you a complete picture of what is going on with my pc. I'm going to look at a way to remove that registry key.
Again, I cannot take permission, I even tried in Safe Mode as the Administrator. I let you know how I make out.
Thanks
With registry key permissions its a bit of a pain to take back control. Generally you need to search for the key its 'calling' generally a dll or whatnot, find it in the registry, change the permissions on THAT key to prevent the virus from takign back control, remove that key thats being called, then go back to the original key that cant be modified, and take control of the *parent* directory then make changes to the problem keys....this is a long drawn out process and i dont envy you on this because it is very frustrating. Basically the root infection file is still active and alive and not being found. This is very common with these type of trojans...it can eventually be removed but if your looking for a gaurantee that it will be gone for good it will never happen. I would highly recommend a rebuild...i hate to say that but these shifting trojans are generally timestamped to reinstall after so many weeks as is...so you never know where the root file is unless you get lucky through poorly designed registry keys.
Sorry to be so vague on this but if you can provide back specifics on what you find throughout your search i will do my best to give you some tips and tricks.
Sorry to be so vague on this but if you can provide back specifics on what you find throughout your search i will do my best to give you some tips and tricks.
The log is OK.
First i wanna look your MRB because you had a rootkit..
Download here MBRCheck http://ad13.geekstogo.com/MBRCheck.exe
Post a fresh log
First i wanna look your MRB because you had a rootkit..
Download here MBRCheck http://ad13.geekstogo.com/MBRCheck.exe
Post a fresh log
Active 4 days ago
Bahpoopie,
I'm taking your advice on the rebuild. As embarrassing as this is I'm the IT / CAD Manager at a small Arch/Eng Company. When my PC got infected, I immediately unplugged it from our network. I'm not a guru such as yourself, but I have cleaned a decent amount of infections on OTHER PEOPLE's computers - but this one is a whopper! Needless to say I cannot afford my PC infected as I'm in and out of servers, workstations, etc. all day.
I did clean the MBR which Symantec detected as "Boot.Tidserv" with a Kaspersky utility. Used Malwarebytes, Superantispyware, Spybot, manual attempts, Blacklight, Hijackthis, numerous rootkt detections - but something else is still there - you run a computer for a few years you can gauge it's speed and how it reacts!
I think you are 100% correct my PC is infected with a hidden virus / rootkit. While attempting to access that registry key, my computer rebooted... just to confirm that it wasn't hardware - which I'm 99% sure it wasn't, I again attempted to access the registry key with GMER - it rebooted - that and your advise it enough for me - I'm re-building it.
Anyway, I'm going to close the case a award you the points - thank you for your help!
I'm taking your advice on the rebuild. As embarrassing as this is I'm the IT / CAD Manager at a small Arch/Eng Company. When my PC got infected, I immediately unplugged it from our network. I'm not a guru such as yourself, but I have cleaned a decent amount of infections on OTHER PEOPLE's computers - but this one is a whopper! Needless to say I cannot afford my PC infected as I'm in and out of servers, workstations, etc. all day.
I did clean the MBR which Symantec detected as "Boot.Tidserv" with a Kaspersky utility. Used Malwarebytes, Superantispyware, Spybot, manual attempts, Blacklight, Hijackthis, numerous rootkt detections - but something else is still there - you run a computer for a few years you can gauge it's speed and how it reacts!
I think you are 100% correct my PC is infected with a hidden virus / rootkit. While attempting to access that registry key, my computer rebooted... just to confirm that it wasn't hardware - which I'm 99% sure it wasn't, I again attempted to access the registry key with GMER - it rebooted - that and your advise it enough for me - I'm re-building it.
Anyway, I'm going to close the case a award you the points - thank you for your help!
Featured Post
Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Most PC repair technicians (if not all) always start their cleanup process by emptying the temp folders before running any removal tools. It makes sense because temp folders are common places for malware installers to lurk and removing all the junk …
Ransomware continues to be a growing problem for both personal and business users alike and Antivirus companies are still struggling to find a reliable way to protect you from this dangerous threat.
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…
- Anti-Virus Apps
- Ransomware
- The Email Laundry
- Email Servers
- Cybersecurity
- Microsoft Access, *malware
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email
Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…
Suggested Courses
Course of the Month8 days, 23 hours left to enroll
764 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.