![]() |
|
#1
|
||||
|
||||
|
I "tested" Rising PC doctor again.
First trojan went straight through. Second one killed and corructed it totally (did not work even after cleaning, perhaps the malware was from China?), and installed a nasty rootkit. System was cleaned by Hitman pro, but the cleaning process needed the install cd. Hitman also found a suspicios file which was indeed part of the infection. I guess I will not test Rising again.... Hitman seems very powerful!
__________________
"Si vis pacem, para bellum" Author of Probably the best free security list in the world |
|
#2
|
|||
|
|||
|
Quote:
![]() |
|
#3
|
||||
|
||||
|
No. Hitman needed to replace an infected system file. I just wonder what happens with OEM-windows owners? Will it work for them too (I mean: is OEM-recovery disk enough)
__________________
"Si vis pacem, para bellum" Author of Probably the best free security list in the world |
|
#4
|
|||
|
|||
|
Quote:
![]() |
|
#5
|
||||
|
||||
|
Quote:
Quote:
Hitman Pro first searches specific folders on the disk to find a white listed variant of the file (Hitman Pro has a white list of all Windows files, stored in the EXE). If the file cannot be found on the system then it prompts for the original CD/DVD. Most AV products do not have this unique feature and just keep the infected system file on the machine. In the near future we plan to add an option for the infected file to be cleaned by one of our partners, resulting in a cleaned file coming from the Scan Cloud. |
|
#6
|
||||
|
||||
|
Quote:
What is a result of this? Is the malware despite of this neutralized? Joe, what would Prevx do here?
__________________
"Si vis pacem, para bellum" Author of Probably the best free security list in the world |
|
#7
|
||||
|
||||
|
Quote:
Prevx 3.0 takes a different approach because most users don't have the original install disks these days (thanks to hardware vendors cutting costs apparently) and most malware is now also searching for copies of the legitimate components and replacing them locally on the system. This is indeed a major and growing problem so we've developed an entire system to handle it, called "System File Replacement" (or "File Replacement Therapy as we like to call it internally ). If we identify that a file is a critical system component and is infected or patched, we download the exact correct copy from our centralized repository. We match the OS, service pack, hotfix level, and language to get the precise file to prevent any OS incompatibilities.This also applies to registry entries - if a system registry entry has been changed or removed, we can replace it (and we have generic routines in place to correct malicious HOSTs file entries and malicious LSP chain entries as well). Let me know if you have any questions with this - system file replacement is one of the many features that we frequently forget to mention ![]() |
|
#8
|
||||
|
||||
|
Quote:
The idea of serving original replacement files from the cloud sounds like the perfect approach but we just do not have the guts (yet ) to distribute original Windows files to our users due to possible legal issues.Last edited by erikloman : August 10th, 2009 at 03:07 AM. |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|