Manual Removal Guide for Haxdoor-H

The following instructions have been created to help you to get rid of "Haxdoor-H" manually.
Use this guide at your own risk; software should usually be better suited to remove malware, since it is able to look deeper.

If this guide was helpful to you, please consider donating towards this site.

Threat Details:

Categories:

• trojan

Description:

Haxdoor-H deactivates the Windows firewall, adds its files as services to the system to have them started at every system start. Haxdoor-H also has the ability to hide several of its files from the windows api, making it hard to detect and remove. ADDITIONAL REMOVING INSTRUCTIONS: Please start Windows in Safe Mode and scan with Spybot S&D again. The remains can be removed only there.

Removal Instructions:

Files:

Please use Windows Explorer or another file manager of your choice to locate and delete these files.

• The file at "<$SYSDIR>\skyx24.sys".
• The file at "<$SYSDIR>\skyx16.dll".
• The file at "<$SYSDIR>\qz.sys".
• The file at "<$SYSDIR>\qz.dll".
• The file at "<$SYSDIR>\klgcptini.dat".
• The file at "<$SYSDIR>\ps.a3d".
• The file at "<$SYSDIR>\config\SSL".
• The file at "<$SYSDIR>\f87ux.ini".
• The file at "<$SYSDIR>\xdudmm.sys".
• The file at "<$SYSDIR>\xdudtt.dll".
• A file with an unknown location named "winm32.dll".
• A file with an unknown location named "winm32.sys".
• A file with an unknown location named "winm64.sys".
• The file at "<$SYSDIR>\avpx32.sys".
• The file at "<$SYSDIR>\avpx64.sys".
• The file at "<$SYSDIR>\qy.sys".
• The file at "<$SYSDIR>\qz.dll".
• The file at "<$SYSDIR>\qz.sys".
• The file at "<$SYSDIR>\redir.a3d".
• The file at "<$SYSDIR>\tnfl.a3d".
• The file at "<$SYSDIR>\p3.ini".
• The file at "<$SYSDIR>\i.a3d".
• The file at "<$SYSDIR>\fltr.a3d".
• The file at "<$SYSDIR>\ps.a3d".
• The file at "<$SYSDIR>\redir.a3d".
• The file at "<$SYSDIR>\p2.ini".
• A file with an unknown location named "drct16.dll".
• The file at "<$SYSDIR>\draw32.dll".
• The file at "<$SYSDIR>\i.a3d".
• The file at "<$SYSDIR>\klogini.dll".
• The file at "<$SYSDIR>\p2.ini".
• The file at "<$SYSDIR>\ps.a3d".
• A file with an unknown location named "RECHNUNG08[1].PDF.EXE".

Make sure you set your file manager to display hidden and system files. If Haxdoor-H uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify files!

Important: There are more files that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Registry:

You can use regedit.exe (included in Windows) to locate and delete these registry entries.

• Delete the registry key "skyx16" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\".
• Delete the registry key "skyx16.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "skyx16.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Minimal\".
• Delete the registry key "skyx16.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Minimal\".
• Delete the registry key "skyx16.sys" at "HKEY_L07-OCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "skyx16.sys" at "HKEY_L07-OCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Network\".
• Delete the registry key "skyx16.sys" at "HKEY_L07-OCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Network\".
• Delete the registry key "skyx16" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "skyx16" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\".
• Delete the registry key "skyx16" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\".
• Delete the registry key "skyx24.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "skyx24.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Minimal\".
• Delete the registry key "skyx24.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Minimal\".
• Delete the registry key "skyx24.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "skyx24.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Network\".
• Delete the registry key "skyx24.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Network\".
• Delete the registry key "skyx24" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "skyx24" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\".
• Delete the registry key "skyx24" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\".
• Delete the registry key "xdudtt" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\".
• Delete the registry key "xdudmm" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "xdudtt" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "xdudmm" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\".
• Delete the registry key "xdudtt" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\".
• Delete the registry key "xdudmm" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\".
• Delete the registry key "xdudtt" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\".
• Delete the registry key "xdudmm.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "xdudtt.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "xdudmm.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "xdudtt.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "xdudmm.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Minimal\".
• Delete the registry key "xdudtt.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Minimal\".
• Delete the registry key "xdudmm.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Network\".
• Delete the registry key "xdudtt.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\SafeBoot\Network\".
• Delete the registry key "xdudmm.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Minimal\".
• Delete the registry key "xdudtt.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Minimal\".
• Delete the registry key "xdudmm.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Network\".
• Delete the registry key "xdudtt.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\SafeBoot\Network\".
• Delete the registry key "avpx32" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\".
• Delete the registry key "avpx32.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "avpx64.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "avpx32.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "avpx64.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "avpx32" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "avpx64" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "avpx32.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\".
• Delete the registry key "avpx64.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\".
• Delete the registry key "avpx32.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\".
• Delete the registry key "avpx64.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\".
• Delete the registry key "avpx32" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\".
• Delete the registry key "avpx64" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\".
• Delete the registry value "<$SYSDIR>\avpx32.exe" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List\".
• Delete the registry value "<$SYSDIR>\avpx32.exe" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List\".
• Delete the registry key "TestService" at "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\MPRServices".
• Delete the registry value "StackSize" at "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\".

If Haxdoor-H uses rootkit technologies, use our RegAlyzer, RootAlyzer or our Total Commander anti-rootkit plugins.

Final Words:

If neither Spybot-S&D nor self help did resolve the issue or you would prefer one on one help,

1. Please read these instructions before requesting assistance,
2. Then start your own thread in the Malware Removal Forum where a volunteer analyst will advise you as soon as available.