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

RootkitReveal


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

#1 Stila_R8dr

Stila_R8dr

  • Members
  • 92 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:15 PM

Posted 15 December 2010 - 04:12 PM

Hello

Today I decided to launch Rootkitreveal, I do not know how to interpret the results, it does not look good although.
It said it found like 60 something things wrong. I don't know how to start or where to ask.

Here is the log, if anyone is interested in looking.

Should I be worried?

Thanks.... Tony

HKU\.DEFAULT\Control Panel\International 3/15/2008 1:52 PM 0 bytes Security mismatch.
HKU\.DEFAULT\Control Panel\International\Geo 3/15/2008 1:52 PM 0 bytes Security mismatch.
HKU\S-1-5-21-329068152-688789844-725345543-500\Console 6/28/2010 8:26 PM 0 bytes Security mismatch.
HKU\S-1-5-21-329068152-688789844-725345543-500\Console\%systemroot%_system32_cmd.exe 6/28/2010 8:26 PM 0 bytes Security mismatch.
HKU\S-1-5-21-329068152-688789844-725345543-500\Console\C:_WINDOWS_system32_kmd.exe 6/28/2010 8:26 PM 0 bytes Security mismatch.
HKU\S-1-5-21-329068152-688789844-725345543-500\Control Panel\International 12/10/2010 11:55 PM 0 bytes Security mismatch.
HKU\S-1-5-21-329068152-688789844-725345543-500\Control Panel\International\Geo 3/15/2008 1:52 PM 0 bytes Security mismatch.
HKU\S-1-5-21-329068152-688789844-725345543-500\Software\SecuROM\!CAUTION! NEVER DELETE OR CHANGE ANY KEY* 7/14/2010 4:13 AM 0 bytes Key name contains embedded nulls (*)
HKU\S-1-5-18\Control Panel\International 3/15/2008 1:52 PM 0 bytes Security mismatch.
HKU\S-1-5-18\Control Panel\International\Geo 3/15/2008 1:52 PM 0 bytes Security mismatch.
HKLM\SECURITY\Policy\Secrets\SAC* 7/11/2007 11:57 PM 0 bytes Key name contains embedded nulls (*)
HKLM\SECURITY\Policy\Secrets\SAI* 7/11/2007 11:57 PM 0 bytes Key name contains embedded nulls (*)
HKLM\SECURITY\Policy\Secrets\SCM:{3D14228D-FBE1-11D0-995D-00C04FD919C1}* 3/24/2010 1:42 AM 0 bytes Key name contains embedded nulls (*)
HKLM\SOFTWARE\Microsoft\Cryptography\RNG\Seed 12/15/2010 12:51 PM 80 bytes Data mismatch between Windows API and raw hive data.
HKLM\SOFTWARE\swearware\backup\winsock2 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5\Catalog_Entries 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000001 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000002 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000003 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000004 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000005 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000001 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000002 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000003 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000004 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000005 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000006 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000007 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000008 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000009 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000010 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000011 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000012 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000013 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000014 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000015 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000016 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000017 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000018 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000019 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000020 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000021 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000022 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000023 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000024 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000025 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000026 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000027 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000028 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000029 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000030 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000031 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000032 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000033 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000034 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000035 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SOFTWARE\swearware\backup\winsock2\Parameters\Protocol_Catalog9\Catalog_Entries\000000000036 5/2/2010 6:42 PM 0 bytes Security mismatch.
HKLM\SYSTEM\ControlSet001\Control\StillImage\Events\STIProxyEvent\{7E9DCE91-2C38-4B27-8081-ED06127B39AD}\Icon 5/20/2010 5:08 AM 45 bytes Data mismatch between Windows API and raw hive data.
HKLM\SYSTEM\ControlSet002\Control\StillImage\Events\STIProxyEvent\{7E9DCE91-2C38-4B27-8081-ED06127B39AD}\Icon 5/20/2010 5:08 AM 45 bytes Data mismatch between Windows API and raw hive data.
HKLM\SYSTEM\ControlSet003\Control\StillImage\Events\STIProxyEvent\{7E9DCE91-2C38-4B27-8081-ED06127B39AD}\Icon 5/20/2010 5:08 AM 45 bytes Data mismatch between Windows API and raw hive data.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,740 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:15 PM

Posted 15 December 2010 - 09:28 PM

Hello yes looks like there is rootkit activity. There are some new variants of rootkits in the wild right now that will require custom scripts to remove the infection, the process must be completed by HJT team members or above.

Failure to follow the proper removal process can and will cause serious damage to a machine. Recovery of the machine may be difficult, if not impossible.

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.
Skip the GMER step,instaed post the Rootkit log you posted earlier.
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

#3 Stila_R8dr

Stila_R8dr
  • Topic Starter

  • Members
  • 92 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:California
  • Local time:08:15 PM

Posted 16 December 2010 - 12:49 AM

Hello

I was able to do what was asked up until....

I got a blue screen stop error while in the middle (i suppose it was middle) of the GMER scan. It all was going great I got up did a few things in the garage. When I returned, expecting to save the log. Instead I had a Blue screen....

Check to make sure any new hardware software is properly installed . updates and stuff and blah blah..
Run the driver verifier against blah blah..
and at the bottom of all the blah dirty blah beepin blah, blah.
stop: 0x000000c5 (0x0000FFFE, 0X00000002, 0X00000000, 0X8054BOBA).... BLAH!

It seemed that the DDS portion went well. I have logs on desktop.

I had to restart.

Should I try again? Should I be worried, now?

Thanks

#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:15 PM

Posted 16 December 2010 - 12:59 AM

Skip the GMER step, instead post the Rootkitreveal log you posted earlier.

No, don't bother with the gmer scan.

Edited by AustrAlien, 16 December 2010 - 01:02 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 quietman7

quietman7

    Bleepin' Janitor


  • Global Moderator
  • 50,941 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia, USA
  • Local time:11:15 PM

Posted 16 December 2010 - 09:48 AM

Your log is posted here.

Now that your log is 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 Response 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 member assisting you and could complicate the malware removal process or make things worst which would extend the time it takes to clean your computer.

From this point on the Malware Response 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 Response 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 posted your log and are waiting, please DO NOT "bump" your post or make another reply until it has been responded to by a member of the Malware Response 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 Malware Response Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic until you are cleared by the Malware Response Team. If you still need assistance after your log has been reviewed and you have been cleared, please PM me or another moderator and we will re-open this topic.

Good luck with your log.

Important Note for future reference:

Rootkit Revealer is a stand-alone tool that will help investigate for the presence of rootkits. It will not actually tell you if you are infected or not unless you know what you're looking for. If you're unsure how to use a particular Anti-rootkit (ARK) tool or interpret the log it generates, then you probably should not be using it. Some ARK tools are intended for advanced users or to be used under the guidance of an expert who can interpret the log results and investigate it for malicious entries before taking any removal action. Incorrectly removing legitimate entries could lead to disastrous problems with your operating system.

Why? Not all hidden components detected by anti-rootkit (ARK) scanners are malicious. It is normal for a Firewall, some anti-virus and anti-malware software (ProcessGuard, Prevx), CD Emulators sandboxes, virtual machines and Host based Intrusion Prevention Systems (HIPS) to exhibit rootkit-like behavior or hook into the OS kernal/SSDT in order to protect your system. SSDT (System Service Descriptor Table) is a table that stores addresses of functions that are used by Windows. Whenever a function is called, Windows looks in this table to find the address for it. Both legitimate programs and rootkits can hook into and alter this table.

API Kernel hooks are not always bad since some system monitoring software and security tools use them as well. If no hooks are active on a system it means that all system services are handled by ntoskrnl.exe which is a base component of Windows operating systems and the process used in the boot-up cycle of a computer. ARK scanners do not differentiate between what is good and what is bad...they only report what is found. Therefore, even on a clean system some hidden essential components may be detected when performing a scan to check for the presence of rootkits. As such, you should not be alarmed if you see any hidden entries created by legitimate programs after performing a scan.

In most cases further investigation is required after the initial ARK scan by someone trained in rootkit detection or with advanced knowledge of the operating system. Report logs need to be analyzed and detected components identified in order to determined if they are benign, system critical or malevolent before attempted removal. Using an ARK scanner without knowing how to tell the difference between legitimate and malicious entries can be dangerous if a critical component is incorrectly removed.

Data mismatch discrepancies will occur if a registry value is updated while the scan is in progress. Values that change frequently include timestamps such as the Microsoft SQL Server uptime value and virus scanner "last scan" values. RKR scans the HKLM\Security\Policy hive which contains SAC* and SAI* hidden keys with embedded (trailing) nulls. This is normal and not a cause for alarm. The presence of some keys with nulls may be pertinent to the correct operation of related applications. The Windows API treats key names as null-terminated strings whereas the kernel treats them as counted strings.There are many free ARK tools but some of them require a certain level of expertise and investigative ability to use. These are a few of the easier ARKS for novice users:Malwarebytes Anti-Malware uses a proprietary low level driver (similar to some ARK detectors) to locate hidden files and special techniques which enable it to detect a wide spectrum of threats including active rootkits. SUPERAntiSpyware Free offers technology to deal with rootkit infections as well.

Edited by quietman7, 16 December 2010 - 09:52 AM.

.
.
Windows Insider MVP 2017-2018
Microsoft MVP Reconnect 2016
Microsoft MVP Consumer Security 2007-2015 kO7xOZh.gif
Member of UNITE, Unified Network of Instructors and Trusted Eliminators

If I have been helpful & you'd like to consider a donation, click 38WxTfO.gif




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users