![]() |
|
#3
|
|||
|
|||
|
Not sure I've heard of this one happening before.
1. Use ScyllaHide plugin to see if you can hide the debugger and check behavior. 2. Set debugger exception ignore range to: 00000000-99999999 3. Disable System BP and Entry BP to see if behavior changes inside debugger. 4. Create a loader to perform patch in-memory. Research links: https://www.apriorit.com/dev-blog/367-anti-reverse-engineering-protection-techniques-to-use-before-releasing-software https://anti-debug.checkpoint.com/ Last edited by Stingered; 02-22-2022 at 04:31. |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Evading behavior analysis | 0xall0c | General Discussion | 3 | 05-14-2018 23:44 |
| armadillo strange behavior | drequinox | General Discussion | 0 | 02-11-2006 08:52 |
| weird search behavior | abitofboth | General Discussion | 0 | 01-30-2005 20:48 |
| A weird debugging question | sgdt | General Discussion | 5 | 06-28-2004 13:11 |