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

win32k.sys been hacked?


  • Please log in to reply
No replies to this topic

#1 Douger

Douger

  • Members
  • 26 posts
  • OFFLINE
  •  
  • Local time:08:02 PM

Posted 17 April 2009 - 03:58 PM

Hello all,

I recently got a call from a user who had a bunch of popups about viruses on her computer. It turned out to be adware that ClamAV identifies as Adware.Fakealert-560, and as Trojan.FakeAV-90. I used ClamAV and AdAware on the machine and that seemed to clean things. I ran HijackThis afterwards and found another suspiscious file still in there, and managed to get rid of that as well. I run MJRegwatcher on the PCs I manage and set it for "Accept all" as I found the users couldn't deal with the false positives it would throw at them when set to Prompt. I wanted to use it for forensic study if needed and after I managed to get rid of everything, there is one entry in the regwatcher log that has me concerned. It is:

** Friday 4/3/2009 4:10:20 PM **
File Details Changed from
c:\winnt\system32\win32k.sys - Size=1,644,432 Date=Sun Sep 14 23:13:42 2008 Attributes=---A-
to
c:\winnt\system32\win32k.sys - Size=1,644,784 Date=Sun Feb 08 10:16:49 2009 Attributes=---A-

What I can't seem to find on the MS support site is the correct file information for this file. This may have been an automatic update that occurred at this time, I'm not sure. RootkitRevealer does not show any problems regarding this file, just three registry entries that are already discussed in that forum as being false positives.

This entry is immediately followed in the regwatcher log by entries that are obviously related to the fake adware that infected the machine. However this could be coincidental with the booting up of the computer after the infection occurred.

The OS is Windows 2000 SP 4 .

Any cause for concern?

Thanks for the look.

Doug

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users