Ollydbg v2 antidetect issue for OutputDebugStringA about scyllahide HOT 2 CLOSED

It's being detected because Olly is... special. x32dbg and the CLI injector don't have this problem, but more suspiciously I couldn't reproduce this in Olly v1 either. After further investigation it turns out the Olly v1 plugin literally hooks the entire debug event loop just to fix Olly's broken exception handling. I've carried over this very... interesting... hack code to the v2 plugin, so the test will now pass.

BTW, why is this option grayed out inside the Ollydbg v1?

Because of this piece of code:

#ifdef OLLY1
  EnableWindow(GetDlgItem(hWnd, IDC_OUTPUTDEBUGSTRINGA), FALSE);
#endif

Using my psychic powers however, I deduce that your next question will now be 'why is that code there?'. The answer to that is: I have no fucking clue :)

from scyllahide.

I'm not even sure why this is still an option... I think the issue is related to https://bitbucket.org/titanengineupdate/titanengine-update/src/e089f4af41a461b69017db3750f79fbaed1008df/TitanEngine/TitanEngine.Debugger.DebugLoop.cpp?at=master&fileviewer=file-view-default#TitanEngine.Debugger.DebugLoop.cpp-390 and maybe this was fixed in olly2 🤞 ?

from scyllahide.