spy1
Full Member
  
 I love YaBB 1 Gold!

Gender: 
Posts: 231
|
 |
Re: TH Guard and P2P
« Reply #4 on: Jun 11th, 2008, 6:39am » |
Quote Modify
|
Hi, Jrb! Not really what I had in mind. A purposeful, self-initiated install of anything doesn't reflect the same conditions as a file download that tries to install itself with evil, stealthy intent, I don't think (I could be wrong). Besides - even SpyCop wouldn't detect it unless you actually ran a scan with it, would it? Which would be way after-the-fact of the keyloggers' installation? What I'm looking for here is examples of prevention - not after the fact detection, if you know what I mean. That's why I refer to TH's Guard and not the scanner. Hey, hope all is well with you! Pete *Of course, since you piqued my curiousity, I went ahead and installed the Ardamax keylogger from its' homepage. The set-up exe itself didn't trigger any alarms from anything here (TH Guard running, NOD32 monitoring), nor did a single file scan by TH itself, or NOD32, OR SpyCop indicate any malware. The installation itself went off without a hitch or an alarm by any of those three programs (although my Sunbelt Personal Firewall did ask for permission for it to install, which I gave). Ardamax keylogger, once installed, runs with "PDM.exe" showing in Process Explorer and with a SYSTRAY icon (which can be hidden to NOT show). And it IS faithfully recording this as I type it here. (My S.P.F asked for permission to open "AKV.exe" when I double-clicked the keyloggers' SYSTRAY icon to see whether it was working or not, which I allowed). Not very comforting so far, is it? Never fear - NOD32 kicked its' butt when I scanned it with TH's scanner: 6/11/2008 8:40:01 AM Real-time file system protection file C:\Program Files\PDM\PDM.exe a variant of Win32/KeyLogger.Ardamax application cleaned by deleting - quarantined NT AUTHORITY\SYSTEM Event occurred during an attempt to access the file by the application: C:\Program Files\TrojanHunter 5.0\TrojanHunter.exe. The keyloggers' tray icon blinked out and its' process dis-appeared from Process Explorer. I have a feeling that NOD32 would have picked it up sooner, but I didn't have "Potentially Unwanted" or "Potentially Unsafe" applications check-marked in NOD until more than halfway through its' scan. If I have time, I'll shut NOD down, re-install the keylogger and try the TH scan again. Pete
|