Yes, follow Pondus's suggestion. By the way here is info on one of the malcreations mentioned:
Backdoor.Generic.459002:
http://vil.nai.com/vil/content/v_132798.htmAnd here avast added detection in a more recent report:
http://www.virustotal.com/file-scan/report.html?id=1f5b7c646092641618b79557a47dcc8eba3f96d8f82673568d9d124f5c3fd90a-1285496755Here a removal procedure for one of the keyloggers:
Kill processes:
889807c35d0a25da35739a87b5c80cf5.exe, keylogeditor.exe, mshe1p.exe, rds.exe, trojanspy.win32.delf.af.exe, trojanspy.win32.delf.af[2].exe, trojanspy.win32.delf.ar.exe, trojanspy.win32.delf.bw.exe, trojanspy.win32.delf.i.exe, trojanspy.win32.delf.m.exe, trojanspy.win32.delf.o.exe, trojanspy.win32.delf.t.exe
Unregister DLLs:
trojanspy.win32.delf.ar[2].dll, trojanspy.win32.delf.cb.dll, trojanspy.win32.delf.n.
Delete files:
889807c35d0a25da35739a87b5c80cf5.exe, keylogeditor.exe, mshe1p.exe, rds.exe, trojanspy.win32.delf.af.exe, trojanspy.win32.delf.af[2].exe, trojanspy.win32.delf.ar.exe, trojanspy.win32.delf.bw.exe, trojanspy.win32.delf.i.exe, trojanspy.win32.delf.m.exe, trojanspy.win32.delf.o.exe, trojanspy.win32.delf.t.exe, trojanspy.win32.delf.ar[2].dll, trojanspy.win32.delf.cb.dll, trojanspy.win32.delf.n.
polonus