Workshop Demonstrates ConfuserEx .NET Anti-Debugging and Analysis
· 13:55 · Watch on YouTube ↗
Summary
A workshop demonstrates how ConfuserEx 2 adds .NET anti-debugging logic to a module constructor, how DE4 helps make obfuscated code easier to inspect, and how repeated debugger checks complicate analysis.
Key points
- ConfuserEx 2 applies protections such as anti-debugging and anti-dumping to compiled binaries through a project configuration file.
- In the demonstration, anti-debugging logic is inserted into a module constructor, which runs before the program’s main entry point.
- Unicode-based symbol names make the obfuscated code harder for a human analyst to interpret.
- The demonstrated anti-debug logic checks for profiling, then runs continued debugger checks on a background thread and terminates the process if detected.
- DE4 detects ConfuserEx and renames obfuscated symbols, improving readability; the presenter notes it does not remove the demonstrated anti-debugging logic.
- The workshop discusses manually modifying a binary or analyzing it after runtime deobfuscation as ways to work around layered anti-analysis.
Article Details
- Topics
- [00:00] Configuring ConfuserEx 2 protections for a compiled .NET binary
- [02:02] Anti-dump behavior and the workshop’s focus on anti-debugging
- [04:14] Anti-debugging logic in a module constructor and Unicode-based obfuscation
- [07:47] Using DE4 to detect ConfuserEx and rename obfuscated symbols
- [11:05] Profiling checks and continuous background debugger detection
- [13:02] Layered anti-analysis and approaches to inspect or dump program code
