secrary / makin

makin - reveal anti-debugging and anti-VM tricks [This project is not maintained anymore]
https://secrary.com
MIT License
732 stars 147 forks source link

[EXCEPTION] EXCEPTION_ACCESS_VIOLATION #3

Closed ghost closed 6 years ago

ghost commented 6 years ago

Apon using the program, it returns this error twice -

[EXCEPTION] EXCEPTION_ACCESS_VIOLATION

Any help?

I'm very new to reverse engineering, thanks! :)

secrary commented 6 years ago

Can you share the sample?

ghost commented 6 years ago

Here's the program I'm trying to debug - https://mega.nz/#!MTQnHT5S!VywIRyKWxFAkMAUmwrFFGjfZQvFgOU62yQ6pxSJVjo8

Thanks for the quick reply

secrary commented 6 years ago

The sample is protected by Obsidium software protection system, maybe it checks the existence of a debugger via reading PEB.BeingDebugged field or something similar and behaves differently, at this moment makin cannot detect such direct memory accesses, or maybe that's an intended exception to detect if a debugger is there or not

ghost commented 6 years ago

Okay thanks! Just for some help, how did you figure out it was protected by Obsidium?

secrary commented 6 years ago

Using this tool: http://exeinfo.atwebpages.com/

ghost commented 6 years ago

Thanks for all the help 👍 I've just started learning reverse engineering and it's all really confusing right now.

secrary commented 6 years ago

I recommend this book: https://beginners.re/RE4B-EN.pdf for RE