Memory write watch anti-debug #101
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Detects external memory accesses by debuggers and hooks using the MEM_WRITE_WATCH feature of VirtualAlloc, using 4 different approaches.
|
I'm aware that this isn't the best right now. I need to improve this at a later date, checking against better APIs and more of them, and using ResetWriteWatch instead of page access count deltas. For now this will suffice as a baseline. |
Make sense to me as well. A new trick! thanks a lot again for your contribution, I never seen this one before, thank you so much for your blog article. |
|
No probs. Yeah, I thought of this in the shower haha! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using VirtualAlloc's MEM_WRITE_WATCH and associated APIs to look for hooks and debuggers.
Writeup here:
https://codeinsecurity.wordpress.com/2018/01/24/anti-debug-with-virtualallocs-write-watch/