Hacker News new | ask | show | jobs
by 8chanAnon 1052 days ago
The Javascript statement is simply "debugger". Very easy to abuse. Of course, there are other techniques for breaking devtools. There are JS libraries designed for the purpose of detecting that the dev console is open. The response may be to run the debugger command, freeze the code, reload the web page or, worse, do some serious hanky-panky (it's not hard to crash the web browser; an endless loop can do that).
1 comments
matheusmoreira 1052 days ago
> Problem is that the devtools are not available due to the repeated abuse of the debugger and console clear commands.

What methods do they use to detect debugging tools and how do we defeat them?

link
IshKebab 1051 days ago
Timing analysis is probably going to be the most reliable and annoying. I've heard they also detect when the window size suddenly changes, but that sounds ridiculously fragile and easy to defeat.

Difficult to imagine any anti-debugging techniques that will work against something that just records an execution trace.

link
russelg 1052 days ago
They don't need to detect the devtools being open, debugger is a no-op when the devtools aren't open so you can just run it in a loop forever.
link
8chanAnon 1052 days ago
The debugger command abuse can be defeated (as already mentioned in this thread). A devtool detector is used in order to invoke stronger blocking methods such as forcibly reloading the web page until the console is closed.
link
8chanAnon 1052 days ago
Search on GitHub. I don't know how to defeat them. I just don't use dev tools.
link