SysInternals Releases RootkitRevealer 260
Brian writes "In the wake of news that Microsoft is developing prototype software to detect rootkits, SysInternals has released a free rootkit detection tool named RootkitRevealer for all Windows systems NT4+. RootkitRevealer works by "comparing the results of a system scan at the highest level with that at the lowest level," and detects every known rootkit at rootkit.com. They also report that it is impossible to know for sure that a given system is clean from within it, but that defeating their tool would require a level of sophistication not yet seen. You can download RootkitRevealer."
Strange... (Score:5, Funny)
Probably nothing to worry about.
Re:Strange... (Score:5, Informative)
Re:Strange... (Score:5, Funny)
Re:Strange... (Score:2)
Aside from the fact that the XP firewall is NOT free, it requires you to purchase a copy of XP in order to use it, therefore it's a component of a non-free product.
Re:Strange... (Score:2, Informative)
Re:Strange... (Score:2, Informative)
Re:Strange... (Score:2)
Sysinternals is great (Score:5, Informative)
No really, they have class utilities for free, thanks Sysinternals
Re:Sysinternals is great (Score:5, Insightful)
One can note that Microsoft is stopping some kinds of hooking of individual kernel functions in the AMD64 release of XP. It's motivated by the fact that it won't break binary compatibility with existing code, as it would be broken anyway, and that it leads to sounder use of the API. It makes some rootkitting harder, and tools like regmon (not filemon, as it can hook as a filesystem filter driver). It doesn't make any of it impossible, though. It should really be noted that some of the low-level tools from sysinternals use very similar techniques to what a rootkit would do, just that they do it for monitoring and not with falsification of data as intent.
Incompatible? (Score:5, Insightful)
I can see it now. The future Microsoft product (which might come free with the OS) will say this other tool is a rootkit and remove it. This area of security should be very interesting to watch.
Re:Incompatible? (Score:4, Interesting)
Re:Sysinternals is great (Score:2, Informative)
Bloated Software Giant Ahead of the Curve Again (Score:5, Funny)
Wow. Pop-up blocking, rootkit detection, basic network security... isn't it amazing how an enormous patent library and billions of dollars encourages so much innovation? It's like they're ten years ahead of everyone else.
Wait... no, the other way around...
Free Sony PSPs [tinyurl.com]. It's real. It's here.
Rootkit? (Score:5, Funny)
Re:Rootkit? (Score:5, Insightful)
Re:Rootkit? (Score:4, Funny)
Re:Rootkit? (Score:3, Funny)
Personally, if that occurs, I favor dynamite charges over either of the above.
So this is... (Score:5, Funny)
So this is a rootkit in itself.
I don't know that I'd trust Microsoft anymore than anyone else running rootkits on my ststem.
Re:So this is... (Score:4, Informative)
RootKitRevealer doesn't change any results of API calls at all.
RootKits are a fairly precisely-defined thing, I don't think there's as much grey area here as you think there is.
handy (Score:5, Insightful)
You know, Microsoft is securing (really) XP with the SP2, popups-blockers, restrictions on activex objects....which is great, but Microsoft has allowed a whole industry to grow - the spyware industry. There's lot of money there and they aren't going to stop so easily, they'll try other methods, and the fact that 99% of XP users runs with administrator privileges is too sexy, it allows you to reach the kernel, where you're god and you can bypass spyware/virus programs...(and if today's spyware is very poorly designed and can break your IE eve when they don't really wnat that, guess how systems will start to break if rootkits are started to use....)
Re:handy (Score:2)
Speaking of running as Administrator, or having to in some cases, did you ever see the docs that show the hoops you have to go through to run Visual Studio as a non-administrator non-Admin [microsoft.com]? While I cannot speak for Delphi 2005, Delphi 7 has this same problem to some extent. Sometimes it's a pain in the ass to not run as Administrator. That needs to be fixed.
Re:handy (Score:2)
The "Designed for Windows XX" logo signifies (at least in the NT variants) that a program can be run by anyone in the User group. I read somewhere what this entails (not writing to certain portions of the registry comes to mind), but I'm sure someone will followup with that information.
I can understand VS not running under the User group -- there's a need to develop for users who aren't going
Re:handy (Score:4, Interesting)
Re:handy (Score:2)
The Microsoft Catalogue lists products which meet the "designed for" standards. This search [microsoft.com] should find Office 2003, note the "Designed For" logo to the right. You can do similar searches for other products (I checked Office XP) - everything I looked up was certified.
Re:handy (Score:2)
Re:handy (Score:4, Interesting)
Re:handy (Score:2)
Re:handy (Score:2)
think of spyware as the common cold- ever evolving, practically undefeatable, but essentially just a periodic nuisance that keeps the immune system on its toes...
Re:handy (Score:3, Insightful)
Even a system with zero exploits will not be safe from an incautious/careless user with the admin password. Even if all IE, ActiveX, etc holes are plugged, malware will still be installed piggy-backing on or masquerading as legitimate software installations.
MS ha
Re:handy (Score:2)
Seriously, how do you expect to be able to run as non-admin when something as simple as The Sims needs to be admin so it can download the latest patches (which are released about once a week or so)?
Re:handy (Score:2)
Re:handy (Score:2)
Looking forward... (Score:5, Funny)
What, until tomorrow?
Re:Looking forward... (Score:2)
Now that's some interesting circular logic.
"We haven't seen the kind of rootkit that we wouldn't be able to detect. Therefore such a rootkit does not exist. QED."
-Adam
If you run linux (Score:5, Informative)
Re:If you run linux (Score:4, Informative)
"chkrootkit has been tested on: Linux 2.0.x, 2.2.x, 2.4.x and 2.6.x, FreeBSD 2.2.x, 3.x, 4.x and 5.x, OpenBSD 2.x and 3.x., NetBSD 1.6.x, Solaris 2.5.1, 2.6, 8.0 and 9.0, HP-UX 11, Tru64 and BSDI."
Re:If you run linux (Score:5, Informative)
Re:If you run linux (Score:2)
Re:If you run linux (Score:2)
You'd have to keep your home directory on a network or removable drive though, and only install programs when disconnected from the net.
Re:If you run linux (Score:2, Insightful)
Re:If you run linux (Score:2)
Initial reading implies rkhunter is, "...more user-friendly and comprehensive...". See This PDF [evoknow.com] (Dealing with Rootkit Attacks on Linux).
LOL (Score:2, Funny)
So its kinda like telling my computer to turn its head and cough, right? *squeeze*
Netcraft has announced; "God exists" (Score:2, Funny)
Forget the vatican and mecca, point your browsers to http://www.sysinternals.com and pay homage.
About the software (Score:2, Interesting)
Re:About the software (Score:4, Informative)
Short answer - no. It will flag stuff that is hidden from the Native Windows API but not everything that's hidden is bad.
It's kind of a moot point anyway. If you find that you've been rootkitted you shouldn't try and clean it. You should reach for your original install media and start over.
Alternatively, take off and nuke the site from orbit. Apparently it's the only way to be sure.
Re:About the software (Score:2)
Rootkit Ben Kanobi says... (Score:2, Insightful)
This really does feel like raising the stakes (or poking a bear with one, regardless).
Unavoidable, I suppose. <sigh>
Re:Rootkit Ben Kanobi says... (Score:2)
You're right, of course. I'd suggest that we're pretty much there already, aren't we? I mean, dicking around with the OS is so plainly off limits (or should be) that anyone planting code like that should be just hauled out back and shot.
Like a partition? (Score:2)
Re:Like a partition? (Score:2)
Re:Like a partition? (Score:4, Interesting)
No way will it let you remove itself. If you boot off of some sort of safe media and delete the thing, the computer no longer has the ability to read any of its data.
Yeah, I know I messed up the jargon, but I'm sure I'll be corrected on that. :P
Re:Like a partition? (Score:2)
Of course, it sounds like you're referring to one running under windows, which means at least part of the filesystem would need to be unencrypted for windows to be able to load and then load the virus drivers (well, unless the virus could somehow place its own load before windows... but I'm not sure how feasible that would be). So otherw
Re:Like a partition? (Score:3, Insightful)
It would be hard to hide from any Linux Live CD's. You boot a read only file system (not modifiable by a bug), load a trusted application (FDISK or Disk Druid) and check the partition table. Not much can hide from a scan from a non-compromised OS.
Microsoft BSA (Score:5, Informative)
Re:Microsoft BSA (Score:2)
**cough**
Someone's got root... and I don't think it's me (Score:2, Interesting)
how about a live cd? (Score:2, Interesting)
RootKit in windows? (Score:2)
Re:RootKit in windows? (Score:5, Funny)
For the same reason trackpads, wireless pointing devices, and such are called "mice", even though they look nothing like a mouse.... why solid state storage devices are called "flash disks" or "flash drives", even though there's nothing flat and circular in them and no moving parts... why the stuff in the middle of pencils is called the "lead", even though it's mostly graphite... why magazines featuring stories told with sequential art are called "comic books", even though they're usually not humorous.
Simple, really (Score:5, Informative)
Why are they called rootkits in windows, when the superuser is called "administrator" and not "root"?
The entity/app/device known as a rootkit was first popularized (so to speak) as a way for the intruder to hide his tracks and maintain root access on a Unix machine. If rootkits had first become popular (again, so to speak) on Win32 machines they likely would have been called adminkit or similar.
In a general techspeak sense, though, (root == full access); most techies have at least a nodding acquaintance with Unix so the idea of root makes sense regardless of the OS in question.
The cynical part of me would like to mention that in years past there really wasn't much need for rootkits on Win32 machines: if the intruder wanted to keep privileged access it would be relatively simple matter to acquire it again.
Re:Simple, really (Score:2)
That's more optimistic than cynical. It means that security is improving when the black hats have to step it up a notch.
Re:RootKit in windows? (Score:2, Funny)
Re:RootKit in windows? (Score:2)
Reputation Counts (Score:5, Insightful)
When it comes to trust, people put their names on things they know are trustworthy. I can't count the number of times I've felt betrayed by Microsoft's products not doing what they're supposed to do, only to discover a flaw in their product that they knew about but didn't tell so as not to affect sales. I also can't count the number of times utilities such as NTFS for DOS [sysinternals.com] have saved my butt in the field.
Way to go Sysinternals.
Re:Reputation Counts (Score:2)
Yeah, but do we really need to be reminded of their name each time you use one of their commands? There must be some book somewhere that someone at Microsoft wrote that defines how to write command-line utilities in the most annoying method possible.
Agreed that Sysinternals does provide useful utilities, but I think what's being overlooked is that it's left to someone else to provide the basic (rudimentary, actually) toolset Microsoft seems conge
Re:Reputation Counts (Score:2)
Also, with a single dominant detection tool out there, it would make the lives of rootkit authors much easier since they'd only need to test their kit against one tool and make sure that tool couldn't detect it.
No info on what the results mean! (Score:2)
Re:No info on what the results mean! (Score:2)
Re:No info on what the results mean! (Score:2)
Just a thought, perhaps a stupid one.
* Pristine meaning OS + your supposed patch level, assuming you can achieve that.
Paranoid? (Score:3, Interesting)
Re:Paranoid? (Score:2)
So don't give users root access. You don't need some sort of hardware DRM crap to do that.
>you'll never have a completely safe system
Why would shifting more responsibility onto a vendor that's legendary for shipping buggy, insecure software make the system more secure?
I'm not sure if it would help (Score:2)
Google and Sysinternals... (Score:3, Interesting)
If I were Google, I'd buy Sysinternals and have them help build GoogleOS.
Sysinternals.com is a Good site (Score:5, Informative)
Here are some good tools of their that I use frequently
Autoruns
http://www.sysinternals.com/ntw2k/freeware/autorun s.shtml [sysinternals.com] shows a complete list of programs that start up automatically when windows starts.
Filemon
http://www.sysinternals.com/ntw2k/source/filemon.s html [sysinternals.com] Filemon shows all filesystem access, so you can see which files programs are accessing. I have found it very useful in diagnosing software problems and fighting spyware.
Regmon
http://www.sysinternals.com/ntw2k/source/regmon.sh tml [sysinternals.com] Like filemon, but for registry access. Shows keys being read and created.
Pagedefrag
http://www.sysinternals.com/ntw2k/freeware/pagedef rag.shtml [sysinternals.com] Defrags the registry hive (most of the registry is stored on disk but is not typically defragmented by many tools) and paging file.
Also many others here
http://www.sysinternals.com/ntw2k/utilities.shtml [sysinternals.com]
IMHO any windows admin should have this stuff installed. Many of the utils come with source code.
Got about 15 "Access is denied" results (Score:2)
How do you REMOVE a rootkit? (Score:4, Insightful)
Re:How do you REMOVE a rootkit? (Score:5, Informative)
This irony here is that it's what you have to do to be 100% sure that no rootkits exists in ANY OS.
Re:How do you REMOVE a rootkit? (Score:4, Funny)
For the Average User, Worthless (Score:3, Interesting)
I wonder how well this would work. (Score:2, Insightful)
Re:I wonder how well this would work. (Score:3, Informative)
Stealth: ALL rootkits are stealth (hide their presence). That's the whole point of a rootkit.
Dead space: Rubbish, data in dead space is never executed. It would have to be bootstrapped by normally visible code which is detected in the usual ways.
Bad secto
Rootkits and the Sysinternals product. (Score:3, Interesting)
Root
In australia, root has several meanings, not at all nice. The sense is similar to f**k.
Accordingly something like root user has the connetation of one that roots your system.
SysIntern RootKitRevealer
I have a fairly typical multi-boot system, with two FAT16 partitions, a FAT32 partition, a reserved BeOS partition, a HPFS partition, and the usual swag of NTFS partitions.
The disk has been showing signs of corruption [bad sectors], and a replacement is in hand: already bought, but there are some backup questions.
RootRevealer had problems scanning registry. (i suspect one of the registristry hives is not well placed on the filesys). On the other hand, i ran the thing from BartPE, (it works), it revealed a whole swag of OS/2 binaries, but i don't know if OS/2 or Windows placed them there. They were meant to be there, by the way. Apart from the metadata files in each partition, there were error messages from non-accessable partitions (like F: (hpfs) and H: (unformatted = beos).)
memory hog (Score:3, Insightful)
Now, if I had to defeat this detection utility, maybe all I need is something that monitors processes that use RAM in this fashion.
Re:A level of sophistication? (Score:2, Insightful)
Re:A level of sophistication? (Score:5, Informative)
Re:A level of sophistication? (Score:2)
Always a good suggestion.
That being said, what is preventing a trojan from digging into the MBR (old virus-style), then running in memory upon HDD boot and launching the rest of its code from an "unused" section of the drive?
Of course, there are problems: Not mu
Re:A level of sophistication? (Score:2, Informative)
The problem is that Windows takes over completely - it switched into protected mode, overwrites all memory and generates its own interrupt vector table. Hiding from Windows wouldn't be too hard - you'd just hook the Bios to tell it not to use bits of memory when NTDETECT runs. The problem would be getting your code to run after Windows loads.
Ac
An argument in favor of NTFS (Score:2)
If it had to unravel NTFS to do its dirty work, that would make it a larger and more error-prone piece of code.
Yeetch, that would be a nasty one. Ghostbuster wouldn't detect it. You'd need a boot CD that looked at all the boot records and maybe even comp
Re:An argument in favor of NTFS (Score:2, Informative)
Most people who run XP don't use a bootmanager, so the mere presence of one should be enough to ask the user why it's there, with the default action to disable it by installing the standard MBR / bootsector.
Oh, and microsoft kernel mode binaries are public key signed since windows 2000, so you don't need MD5/SHA - you can see if they are haxored or not
Re:A level of sophistication? (Score:2, Insightful)
Re:A level of sophistication? (Score:2)
Re:Better solution. (mod parent up!) (Score:3, Interesting)
Re: (Score:2)
Re:Better solution. (Score:2)
Re:Better solution. (Score:2, Informative)
Re:Better solution. (Score:2)
Re:Call to arms (Score:3, Informative)
Re:Call to arms (Score:3, Insightful)
Other than nothing that RootkitRevealer is not a rootkit itself, it's also nice to see that Sysinternals knows the weakness of their products, how it can be exploited, and how it is very very unlikely that it will be.
Re:my office pc is infected = howto remove? (Score:4, Informative)
Seriously though, at least two of those are listed in the article as being fine. Looking over the list, I don't see anything suspicious, and I have many of the same things listed for my system. Although if I'm reading that third line right, you have 9 GBs of bad clusters. You might want to scandisk.
Your system is fine... (Score:5, Informative)
Not to mention that if you have a rootkit installed, you better be prepared to wipe your system clean and reinstall the OS, because otherwise there's no way of knowing if you have the whole thing removed.