Trojaner: Trojan.Heur.Vundo

  • Hallo liebes Forum Team

    Nach der Angebotenen Hilfe von Markusg via Twitter nehme ich diese gerne an.

    Ich habe seit gestern einen Trojaner auf meinem Laptop laut dem BitDefender QuickScan hat dieser den Namen "Trojan.Heur.Vundo.cu4@d4CKyXk" und sitzt hier: C:\WINDOWS\system32\H8SRTruwnrrpbqb.dll

    Hier mal der ganze BitDefender Log:

    BitDefender QuickScan Beta 32-bit v0.9.9.0
    ------------------------------------------

    Überprüfungsdatum: Mon Jan 18 18:15:54 2010
    Computer ID: A0E8CE4B


    1 infizierte Datei gefunden!
    ------------------------------
    C:\WINDOWS\system32\H8SRTruwnrrpbqb.dll - Gen:Trojan.Heur.Vundo.cu4@d4CKyXk

    Einmal editiert, zuletzt von Volkmar (13. Mai 2018 um 10:03)

    • Anzeige

    Hallo!

    Wenn du gerade an deiner Website arbeitest oder dein aktuelles Hosting überdenkst: Wir betreiben mit NetzLiving eine Hosting-Plattform, die speziell auf Performance, Sicherheit und einfache Verwaltung ausgelegt ist.

    • ✔️ Schnelle Ladezeiten (optimiert für WordPress, WoltLab & Co.)
    • ✔️ Deutsche Server & DSGVO-konform
    • ✔️ Persönlicher Support (kein 0815-Ticket-System)

    Mehr erfahren

  • Nun wollte die Liste des Forums abarbeiten jedoch tauchte schon ein Problem auf. Nach der Installation von Malwarebytes Anti-Malware konnte ich das Programm nicht öffen uns somit auch keinen Scan durchführen.

    Bei RSIT hat alles geklappt und hier sind die beiden Logs:

    Der Log:

    Logfile of random's system information tool 1.06 (written by random/random)
    Run by xxx at 2010-01-18 18:04:59
    Microsoft Windows XP Professional Service Pack 3
    System drive C: has 1 GB (1%) free of 108 GB
    Total RAM: 1014 MB (43% free)

    Logfile of Trend Micro HijackThis v2.0.2
    Scan saved at 18:06:25, on 18.01.2010

    Einmal editiert, zuletzt von Volkmar (13. Mai 2018 um 10:04)

  • Malwarebytes lässt sich nicht öffnen das ist das Problem somit kann ich auch keinen Log Posten!

  • Vllt stell ich mich blöd an aber der erste Downloadlink geht nicht und beim zweiten speichere ich lediglich ein Firefoxdoc.

  • Download hat funktioniert jetzt jedoch erscheint ein Error nach dem ich auf Ausführen geklickt habe der sagt: "Some installation files are corrupt. Please download a fresh copy and retry the installation"

    Und nu? :P

  • Hat geklappt! Hier der Log:


    SDFix: Version 1.240
    Run by Administrator on 18.01.2010 at 20:42

    Microsoft Windows XP [Version 5.1.2600]
    Running From: C:\sdfix

    Checking Services :


    Restoring Default Security Values
    Restoring Default Hosts File

    Rebooting


    Checking Files :

    Trojan Files Found:

    C:\autorun.inf - Deleted
    C:\autorun.PNF - Deleted


    Removing Temp Files

    ADS Check :


    Final Check :

    catchme 0.3.1361.2 W2K/XP/Vista - rootkit/stealth malware detector by Gmer, GMER - Rootkit Detector and Remover
    Rootkit scan 2010-01-18 21:06:39
    Windows 5.1.2600 Service Pack 3 NTFS

    scanning hidden processes ...

    scanning hidden services & system hive ...

    disk error: C:\WINDOWS\system32\config\system, 1381
    scanning hidden registry entries ...

    disk error: C:\WINDOWS\system32\config\software, 1381
    disk error: C:\Dokumente und Einstellungen\xxx\ntuser.dat, 1381
    scanning hidden files ...

    disk error: C:\WINDOWS\

    please note that you need administrator rights to perform deep scan

    Remaining Services :


    Authorized Application Key Export:


    Remaining Files :


    File Backups: - C:\SDFix\backups\backups.zip

    Files with Hidden Attributes :


    Finished!

    Einmal editiert, zuletzt von Volkmar (13. Mai 2018 um 10:05)

  • nicht so wie ich gern wollte.
    kannst du mal combofix löschen, wieder in den abgesicherten modus mit netzwerktreibern, dann combofix erneut laden und versuchen, das programm auszuführen.

  • Ums richtig zu verstehen:
    Also Compofix sprich die 1234.exe datei von dir vorhin löschen oder deinstallieren?
    Und dann im abgesicherten Modus mit treibern diese datei wieder neu installieren un schaun ob sie läuft. Richtig?

  • genau, einfach löschen, in den abgesicherten modus starten, downloaden und schauen ob sie dort läuft. wenn nicht müssen wir das mal auf morgen verschieben.

  • Ich werd's probieren nur dachte ich das ich im abgesicherten Modus keine internetverbindung habe. Aber ich schau mal... Würde sagen sonst probieren wir's morgn Nachmittag weiter aber danke schonmal für deine Geduld ;)

  • So also hab es mal probiert habe da im abgesicherten Modus keine Internetverbindung und kann somit Combofix auch nicht neu downloaden.
    Wie gehts nun weiter?:P

  • Bitte schön


    17:56:50:171 2780 TDSS rootkit removing tool 2.2.2 Jan 13 2010 08:42:25
    17:56:50:171 2780 ================================================================================
    17:56:50:171 2780 SystemInfo:

    17:56:50:171 2780 OS Version: 5.1.2600 ServicePack: 3.0
    17:56:50:171 2780 Product type: Workstation
    17:56:50:171 2780 ComputerName: DELL_LAPTOP
    17:56:50:171 2780 UserName: Klaus
    17:56:50:171 2780 Windows directory: C:\WINDOWS
    17:56:50:171 2780 Processor architecture: Intel x86
    17:56:50:187 2780 Number of processors: 2
    17:56:50:187 2780 Page size: 0x1000
    17:56:50:187 2780 Boot type: Normal boot
    17:56:50:187 2780 ================================================================================
    17:56:50:187 2780 UnloadDriverW: NtUnloadDriver error 2
    17:56:50:187 2780 ForceUnloadDriverW: UnloadDriverW(klmd21) error 2
    17:56:50:234 2780 MyNtCreateFileW: NtCreateFile(\??\C:\WINDOWS\system32\drivers\klmd.sys) returned status 00000000
    17:56:50:375 2780 UtilityInit: KLMD drop and load success
    17:56:50:375 2780 KLMD_OpenDevice: Trying to open KLMD Device(KLMD201000)
    17:56:50:375 2780 UtilityInit: KLMD open success
    17:56:50:375 2780 UtilityInit: Initialize success
    17:56:50:375 2780
    17:56:50:375 2780 Scanning Services ...
    17:56:50:375 2780 CreateRegParser: Registry parser init started
    17:56:50:375 2780 DisableWow64Redirection: GetProcAddress(Wow64DisableWow64FsRedirection) error 127
    17:56:50:375 2780 CreateRegParser: DisableWow64Redirection error
    17:56:50:375 2780 wfopen_ex: Trying to open file C:\WINDOWS\system32\config\system
    17:56:50:375 2780 MyNtCreateFileW: NtCreateFile(\??\C:\WINDOWS\system32\config\system) returned status C0000043
    17:56:50:375 2780 wfopen_ex: MyNtCreateFileW error 32 (C0000043)
    17:56:50:375 2780 wfopen_ex: Trying to KLMD file open
    17:56:50:375 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\config\system
    17:56:50:375 2780 wfopen_ex: File opened ok (Flags 2)
    17:56:50:375 2780 CreateRegParser: HIVE_ADAPTER(C:\WINDOWS\system32\config\system) init success: D24A60
    17:56:50:375 2780 wfopen_ex: Trying to open file C:\WINDOWS\system32\config\software
    17:56:50:375 2780 MyNtCreateFileW: NtCreateFile(\??\C:\WINDOWS\system32\config\software) returned status C0000043
    17:56:50:375 2780 wfopen_ex: MyNtCreateFileW error 32 (C0000043)
    17:56:50:375 2780 wfopen_ex: Trying to KLMD file open
    17:56:50:375 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\config\software
    17:56:50:375 2780 wfopen_ex: File opened ok (Flags 2)
    17:56:50:375 2780 CreateRegParser: HIVE_ADAPTER(C:\WINDOWS\system32\config\software) init success: D24B08
    17:56:50:375 2780 EnableWow64Redirection: GetProcAddress(Wow64RevertWow64FsRedirection) error 127
    17:56:50:375 2780 CreateRegParser: EnableWow64Redirection error
    17:56:50:375 2780 CreateRegParser: RegParser init completed
    17:56:50:921 2780 GetAdvancedServicesInfo: Raw services enum returned 414 services
    17:56:50:921 2780 ScanTDL2Services: Exact detect H8SRTd.sys (h: 1)
    17:56:50:921 2780 RegNode HKLM\SYSTEM\ControlSet001\services\H8SRTd.sys infected by TDSS rootkit ... 17:56:50:921 2780 will be deleted on reboot
    17:56:50:921 2780 DeleteTDL2Service: SafeBoot Minimal doesn't infected
    17:56:50:921 2780 DeleteTDL2Service: SafeBoot Network doesn't infected
    17:56:50:937 2780 RegNode HKLM\SYSTEM\ControlSet002\services\H8SRTd.sys infected by TDSS rootkit ... 17:56:50:937 2780 will be deleted on reboot
    17:56:50:968 2780 DeleteTDL2Service: SafeBoot Minimal doesn't infected
    17:56:50:968 2780 DeleteTDL2Service: SafeBoot Network doesn't infected
    17:56:50:968 2780 File C:\WINDOWS\system32\drivers\H8SRTsoulqphegq.sys infected by TDSS rootkit ... 17:56:50:968 2780 will be deleted on reboot
    17:56:50:968 2780 DeleteTDL2Service: Module enum: Name: H8SRTd. Type: 1
    17:56:50:968 2780 DeleteTDL2Service: Module clone ImagePath, skipping
    17:56:50:968 2780 DeleteTDL2Service: Module enum: Name: H8SRTc. Type: 1
    17:56:50:968 2780 File C:\WINDOWS\system32\H8SRTtyqjejkcmj.dll infected by TDSS rootkit ... 17:56:50:968 2780 will be deleted on reboot
    17:56:50:968 2780 DeleteTDL2Service: Module enum: Name: H8SRTsrcr. Type: 1
    17:56:50:968 2780 File C:\WINDOWS\system32\H8SRTikhbgojytx.dat infected by TDSS rootkit ... 17:56:50:968 2780 will be deleted on reboot
    17:56:50:968 2780 DeleteTDL2Service: Module enum: Name: h8srtserf. Type: 1
    17:56:50:968 2780 File C:\WINDOWS\system32\H8SRTruwnrrpbqb.dll infected by TDSS rootkit ... 17:56:50:968 2780 will be deleted on reboot
    17:56:50:968 2780 DeleteTDL2Service: Module enum: Name: h8srtmsg. Type: 1
    17:56:50:968 2780 File C:\WINDOWS\system32\H8SRTppoaivmhuu.dll infected by TDSS rootkit ... 17:56:50:968 2780 will be deleted on reboot
    17:56:50:984 2780 DeleteTDL2Service: Module enum: Name: h8srtbbr. Type: 1
    17:56:50:984 2780 File C:\WINDOWS\system32\H8SRTdabutmqrfs.dll infected by TDSS rootkit ... 17:56:50:984 2780 will be deleted on reboot
    17:56:50:984 2780 ScanTDL2Services: DeleteEvilService(H8SRTd.sys) success
    17:56:50:984 2780 fclose_ex: Trying to close file C:\WINDOWS\system32\config\system
    17:56:50:984 2780 fclose_ex: Trying to close file C:\WINDOWS\system32\config\software
    17:56:50:984 2780
    17:56:50:984 2780 Scanning Kernel memory ...
    17:56:50:984 2780 KLMD_GetSystemObjectAddressByNameW: Trying to get system object address by name \Driver\Disk
    17:56:50:984 2780 DetectCureTDL3: \Driver\Disk PDRIVER_OBJECT: 86FC6758
    17:56:50:984 2780 DetectCureTDL3: KLMD_GetDeviceObjectList returned 5 DevObjects
    17:56:50:984 2780
    17:56:50:984 2780 DetectCureTDL3: DEVICE_OBJECT: 86F844D8
    17:56:50:984 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F844D8
    17:56:50:984 2780 KLMD_ReadMem: Trying to ReadMemory 0x86F844D8[0x38]
    17:56:50:984 2780 DetectCureTDL3: DRIVER_OBJECT: 86FC6758
    17:56:50:984 2780 KLMD_ReadMem: Trying to ReadMemory 0x86FC6758[0xA8]
    17:56:50:984 2780 KLMD_ReadMem: Trying to ReadMemory 0xE101A940[0x18]
    17:56:50:984 2780 DetectCureTDL3: DRIVER_OBJECT name: \Driver\Disk, Driver Name: Disk
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (0) addr: F75C3BB0
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (1) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (2) addr: F75C3BB0
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (3) addr: F75BDD1F
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (4) addr: F75BDD1F
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (5) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (6) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (7) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (8) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (9) addr: F75BE2E2
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (10) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (11) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (12) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (13) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (14) addr: F75BE3BB
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (15) addr: F75C1F28
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (16) addr: F75BE2E2
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (17) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (18) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (19) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (20) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (21) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (22) addr: F75BFC82
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (23) addr: F75C499E
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (24) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (25) addr: 804F4562
    17:56:50:984 2780 DetectCureTDL3: IrpHandler (26) addr: 804F4562
    17:56:50:984 2780 TDL3_FileDetect: Processing driver: Disk
    17:56:50:984 2780 TDL3_FileDetect: Processing driver file: C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:50:984 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:015 2780 TDL3_FileDetect: C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: Clean
    17:56:51:015 2780
    17:56:51:015 2780 DetectCureTDL3: DEVICE_OBJECT: 86F848A0
    17:56:51:015 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F848A0
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0x86F848A0[0x38]
    17:56:51:015 2780 DetectCureTDL3: DRIVER_OBJECT: 86FC6758
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0x86FC6758[0xA8]
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0xE101A940[0x18]
    17:56:51:015 2780 DetectCureTDL3: DRIVER_OBJECT name: \Driver\Disk, Driver Name: Disk
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (0) addr: F75C3BB0
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (1) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (2) addr: F75C3BB0
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (3) addr: F75BDD1F
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (4) addr: F75BDD1F
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (5) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (6) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (7) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (8) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (9) addr: F75BE2E2
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (10) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (11) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (12) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (13) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (14) addr: F75BE3BB
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (15) addr: F75C1F28
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (16) addr: F75BE2E2
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (17) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (18) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (19) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (20) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (21) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (22) addr: F75BFC82
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (23) addr: F75C499E
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (24) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (25) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (26) addr: 804F4562
    17:56:51:015 2780 TDL3_FileDetect: Processing driver: Disk
    17:56:51:015 2780 TDL3_FileDetect: Processing driver file: C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:015 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:015 2780 TDL3_FileDetect: C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: Clean
    17:56:51:015 2780
    17:56:51:015 2780 DetectCureTDL3: DEVICE_OBJECT: 86F84C68
    17:56:51:015 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F84C68
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0x86F84C68[0x38]
    17:56:51:015 2780 DetectCureTDL3: DRIVER_OBJECT: 86FC6758
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0x86FC6758[0xA8]
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0xE101A940[0x18]
    17:56:51:015 2780 DetectCureTDL3: DRIVER_OBJECT name: \Driver\Disk, Driver Name: Disk
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (0) addr: F75C3BB0
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (1) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (2) addr: F75C3BB0
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (3) addr: F75BDD1F
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (4) addr: F75BDD1F
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (5) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (6) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (7) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (8) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (9) addr: F75BE2E2
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (10) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (11) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (12) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (13) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (14) addr: F75BE3BB
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (15) addr: F75C1F28
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (16) addr: F75BE2E2
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (17) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (18) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (19) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (20) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (21) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (22) addr: F75BFC82
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (23) addr: F75C499E
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (24) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (25) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (26) addr: 804F4562
    17:56:51:015 2780 TDL3_FileDetect: Processing driver: Disk
    17:56:51:015 2780 TDL3_FileDetect: Processing driver file: C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:015 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:015 2780 TDL3_FileDetect: C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: Clean
    17:56:51:015 2780
    17:56:51:015 2780 DetectCureTDL3: DEVICE_OBJECT: 86F84030
    17:56:51:015 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F84030
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0x86F84030[0x38]
    17:56:51:015 2780 DetectCureTDL3: DRIVER_OBJECT: 86FC6758
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0x86FC6758[0xA8]
    17:56:51:015 2780 KLMD_ReadMem: Trying to ReadMemory 0xE101A940[0x18]
    17:56:51:015 2780 DetectCureTDL3: DRIVER_OBJECT name: \Driver\Disk, Driver Name: Disk
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (0) addr: F75C3BB0
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (1) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (2) addr: F75C3BB0
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (3) addr: F75BDD1F
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (4) addr: F75BDD1F
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (5) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (6) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (7) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (8) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (9) addr: F75BE2E2
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (10) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (11) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (12) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (13) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (14) addr: F75BE3BB
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (15) addr: F75C1F28
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (16) addr: F75BE2E2
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (17) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (18) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (19) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (20) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (21) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (22) addr: F75BFC82
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (23) addr: F75C499E
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (24) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (25) addr: 804F4562
    17:56:51:015 2780 DetectCureTDL3: IrpHandler (26) addr: 804F4562
    17:56:51:015 2780 TDL3_FileDetect: Processing driver: Disk
    17:56:51:015 2780 TDL3_FileDetect: Processing driver file: C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:015 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\DRIVERS\disk.sys
    17:56:51:031 2780 TDL3_FileDetect: C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: Clean
    17:56:51:031 2780
    17:56:51:031 2780 DetectCureTDL3: DEVICE_OBJECT: 86F87AB8
    17:56:51:031 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F87AB8
    17:56:51:031 2780 DetectCureTDL3: DEVICE_OBJECT: 86F0FF18
    17:56:51:031 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F0FF18
    17:56:51:031 2780 DetectCureTDL3: DEVICE_OBJECT: 86F0ED98
    17:56:51:031 2780 KLMD_GetLowerDeviceObject: Trying to get lower device object for 86F0ED98
    17:56:51:031 2780 KLMD_ReadMem: Trying to ReadMemory 0x86F0ED98[0x38]
    17:56:51:031 2780 DetectCureTDL3: DRIVER_OBJECT: 86F69AC0
    17:56:51:031 2780 KLMD_ReadMem: Trying to ReadMemory 0x86F69AC0[0xA8]
    17:56:51:031 2780 KLMD_ReadMem: Trying to ReadMemory 0xE188D068[0x1A]
    17:56:51:031 2780 DetectCureTDL3: DRIVER_OBJECT name: \Driver\atapi, Driver Name: atapi
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (0) addr: F73E96F2
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (1) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (2) addr: F73E96F2
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (3) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (4) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (5) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (6) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (7) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (8) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (9) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (10) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (11) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (12) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (13) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (14) addr: F73E9712
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (15) addr: F73E5852
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (16) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (17) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (18) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (19) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (20) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (21) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (22) addr: F73E973C
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (23) addr: F73F0336
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (24) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (25) addr: 804F4562
    17:56:51:031 2780 DetectCureTDL3: IrpHandler (26) addr: 804F4562
    17:56:51:031 2780 KLMD_ReadMem: Trying to ReadMemory 0xF73E6864[0x400]
    17:56:51:031 2780 TDL3_StartIoHookDetect: CheckParameters: 0, 00000000, 0
    17:56:51:031 2780 TDL3_FileDetect: Processing driver: atapi
    17:56:51:031 2780 TDL3_FileDetect: Processing driver file: C:\WINDOWS\system32\DRIVERS\atapi.sys
    17:56:51:031 2780 KLMD_CreateFileW: Trying to open file C:\WINDOWS\system32\DRIVERS\atapi.sys
    17:56:51:031 2780 TDL3_FileDetect: C:\WINDOWS\system32\DRIVERS\atapi.sys - Verdict: Clean
    17:56:51:031 2780 UtilityBootReinit: Reboot required for cure complete..
    17:56:51:031 2780 MyNtCreateFileW: NtCreateFile(\??\C:\WINDOWS\system32\drivers\klmdb.sys) returned status 00000000
    17:56:51:046 2780 UtilityBootReinit: KLMD drop success
    17:56:51:046 2780 KLMD_ApplyPendList: Pending buffer(54CB_71FA, 1032) dropped successfully
    17:56:51:046 2780 UtilityBootReinit: Cure on reboot scheduled successfully
    17:56:51:046 2780
    17:56:51:046 2780 Completed
    17:56:51:046 2780
    17:56:51:046 2780 Results:
    17:56:51:046 2780 Memory objects infected / cured / cured on reboot: 0 / 0 / 0
    17:56:51:046 2780 Registry objects infected / cured / cured on reboot: 2 / 0 / 2
    17:56:51:046 2780 File objects infected / cured / cured on reboot: 6 / 0 / 6
    17:56:51:046 2780
    17:56:51:046 2780 MyNtCreateFileW: NtCreateFile(\??\C:\WINDOWS\system32\drivers\klmd.sys) returned status 00000000
    17:56:51:046 2780 UtilityDeinit: KLMD(ARK) unloaded successfully

  • du hast neu gestartet?
    dann lad jetzt noch mal combofix.
    diesmal versuch den original download link, version oben ist ja schon veraltet. combofix vor dem speichern umbenennen und anleitung beachten, log posten.

  • Weiter gehts...


    ComboFix 10-01-18.03 - Klaus 19.01.2010 18:39:22.1.2 - x86
    Microsoft Windows XP Professional 5.1.2600.3.1252.49.1031.18.1014.513 [GMT 1:00]
    ausgeführt von:: c:\dokumente und einstellungen\xxx\Desktop\12345.exe
    AV: Kaspersky Internet Security *On-access scanning disabled* (Updated) {2C4D4BC6-0793-4956-A9F9-E252435469C0}
    FW: Kaspersky Internet Security *disabled* {2C4D4BC6-0793-4956-A9F9-E252435469C0}
    .

    Einmal editiert, zuletzt von Volkmar (13. Mai 2018 um 10:07)

  • deinstaliere alle virenprogramme außer eines.
    öffne spybot, allgemein, erweitert, werkzeuge resident, teatimer deaktivieren, neu start
    öffne malwarebytes, update, scanner, alle laufwerke, komplett scan, funde löschen, log posten. berichten wie der pc läuft.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!