|
|
| License: | GNU General Public License |
| Author: | David Zimmer <david@idefense.com, dzzie@yahoo.com> |
| CopyRight: | Copyright: 2005 iDefense a Verisign Company |
| Code in Olly.dll is Copyright (C) 2001 Oleh Yuschuk | |
| Download: | http://labs.idefense.com/labs-software.php?show=19 |
|
Hook Explorer This is a small application designed to scan a process looking for IAT or detours style hooks. HookExplorer gives the user several scanning and display options.
If the "scan all exports" checkbox was selected, then HookExplorer will also scan every function found in the images export table for detours style hooks. For dynamically loaded dlls, this may be the only test we can perform on them. Note that this option can take some extra time to perform, and cannot be added to an existing scan on the fly. Once you check this option the current scan will not be updated and you will have to rescan the target process. HookExplorer also supports 4 data display modes to help you examine the data. These options can be applied on the fly and will simply re-display the collected scan data. Internally hooks are stored in 3 collections. The first collection saves references to all functions, the second only cross module hooks, and finally the third which applies a user defined filter list to the results. The display options that relate to these collections are termed:
The IgnoreList is loaded from the file IgnoreList.txt found in the applications home directory. This file lists the dlls which you trust and do not want displayed in the results when using the IgnoreList display option. It is recommended to use the full dll path to your trusted dlls in this file. The ignorelist can be edited in notepad and can be updated on the fly to an existing scan. The edit button on the main interface will launch notepad on the file allowing you to edit it. Once you have made your updates, save your changes and hit the reload button which will reload the file and apply the filter to the current display results. Dependencies Hook Explorer is written in VB6. Your system will need the VB6 runtimes and the Microsoft Common Controls OCX (mscomctl.ocx) Installation Unzip and run. If you get an error that msvbvm60.dll is missing, you will have to install the vb6 runtimes. If mscomctl.ocx is missing you will need to download and register the control. Google is your friend. | |