Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/LAC-Japan/IDA_Plugin_AntiDebugSeeker
Automatically identify and extract potential anti-debugging techniques used by malware.
https://github.com/LAC-Japan/IDA_Plugin_AntiDebugSeeker
anti-debugging ida malware-analysis
Last synced: 4 days ago
JSON representation
Automatically identify and extract potential anti-debugging techniques used by malware.
- Host: GitHub
- URL: https://github.com/LAC-Japan/IDA_Plugin_AntiDebugSeeker
- Owner: LAC-Japan
- License: bsd-3-clause
- Created: 2023-09-11T02:29:26.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-10-21T08:08:28.000Z (22 days ago)
- Last Synced: 2024-10-21T11:09:04.118Z (22 days ago)
- Topics: anti-debugging, ida, malware-analysis
- Language: Python
- Homepage:
- Size: 12.5 MB
- Stars: 110
- Watchers: 3
- Forks: 12
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# IDA_Plugin_AntiDebugSeeker
[Version of Ghidra](https://github.com/LAC-Japan/Ghidra_AntiDebugSeeker)
## Introduction
Through this tool, users can automatically extract potential anti-debugging methods used by malware, making it easier for analysts to take appropriate action.
The main functionalities of this plugin are as follows:
- Extraction of Windows API that are potentially being used for anti-debugging by the malware
(All subsequent API represent the Windows API)
- Extraction of anti-debugging techniques based on key phrases that serve as triggers, as some anti-debugging methods cannot be comprehensively identified by API calls alone.
Additionally, the file that defines the detection rules is designed to easily add keywords you want to detect.
This allows analysts to easily add new detection rules or make changes.
For packed malware, running this plugin after unpacking and fixing the Import Address Table is more effective.
## Requirements
From Ver1.1, PyQt5 installation is required:
```
pip install PyQt5
```
## Installation
Place the following three files under the plugin directory of IDA :
1. **anti_debug.config** (A file containing rules for detecting anti-debugging techniques)
2. **anti_debug_techniques_descriptions.json** (A file containing descriptions of the detected rules)
3. **AntiDebugSeeker.py** (The anti-debugging detection program)
## Usage
**Ctrl + Shift + D (To launch the plugin)**
A screen named “Anti Debug Detection Results” will appear after the analysis is complete.
Anti Debug Detection Results
- Category Name:
API category name defined in the Anti_Debug_API as listed in anti_debug.config.
- Possible Anti-Debug API:
List of detected APIs displayed.
- Address:
Address where the detected API is being used.
- Possible Anti-Debug Technique:
Detection name identified by the keyword defined in Anti_Debug_Technique as listed in anti_debug.config.
- Address:
Address of the first detected keyword.
(Address Transition)
By double-clicking on the detected line, you will jump to the address specified.
**Ctrl + Shift + E (Config File Editing)**
Functionality for checking and editing the contents of anti_debug.config.
After making changes,
click the 'Save' button to save the modifications.
## Support Functions
After running the plugin, detected APIs and keywords are highlighted in different colors.
Additionally, if an API specified in Anti_Debug_API is detected, the category name is added as a comment. Likewise, if a rule name is detected in Anti_Debug_Technique, a description of that rule is added as a comment to the first detected keyword.
## anti_debug.config and anti_debug_techniques_descriptions.json
This config file contains the detection rules that are utilized by AntiDebugSeeker.py.
There are sections named Anti_Debug_API and Anti_Debug_Technique.
**Anti_Debug_API**
**(exact match)** You can freely create categories and add APIs that you wish to detect.
**Anti_Debug_Technique**
**(partial match)** You can set between one to three keywords.
The basic flow of the search is as follows:
1. First, search for the first keyword.
2. If it is found, search within the specified number of bytes (default is 80 bytes) for the second keyword.
3. The same process is then applied for searching for the third keyword.
If you want to set a **custom search range** instead of using the default value, you can specify 'search_range=value' at the end of the keyword you've set.
This allows you to change the search range for each rule you've configured.
anti_debug_techniques_descriptions.json contains the descriptions of the rules defined in the Anti_Debug_Technique section.
The values defined in this file can be referenced on the disassembly screen, allowing you to check the descriptions of the rules.
## List of detectable anti-debugging techniques (Ver1.0)
The following is a list of rule names defined in the Anti_Debug_Technique section of the antidebug.config.
```
HeapTailMarker
KernelDebuggerMarker
DbgBreakPoint_RET
DbgUiRemoteBreakin_Debugger_Terminate
PMCCheck_RDPMC
TimingCheck_RDTSC
SkipPrefixes_INT1
INT2D_interrupt_check
INT3_interrupt_check
EXCEPTION_BREAKPOINT
ICE_interrupt_check
DBG_PRINTEXCEPTION_C
TrapFlag_SingleStepException
BeingDebugged_check
NtGlobalFlag_check
NtGlobalFlag_check_2
HeapFlags
HeapForceFlags
Combination_of_HEAP_Flags
Combination_of_HEAP_Flags_2
ReadHeapFlags
ReadHeapFlags_2
DebugPrivileges_Check
Opened_Exclusively_Check
EXCEPTION_INVALID_HANDLE_1
EXCEPTION_INVALID_HANDLE_2
Memory_EXECUTE_READWRITE_1
Memory_EXECUTE_READWRITE_2
Memory_Region_Tracking
Check_BreakPoint_Memory_1
Check_BreakPoint_Memory_2
Software_Breakpoints_Check
Hardware_Breakpoints_Check
Enumerate_Running_Processes
ThreadHideFromDebugger
NtQueryInformationProcess_PDPort
NtQueryInformationProcess_PDFlags
NtQueryInformationProcess_PDObjectHandle
NtQuerySystemInformation_KD_Check
```
## Updated
Jun.24,2024 Ver1.1 Released