5

This website blocks all use of chrome dev tools while logged in to the site. Opening dev tools while logged in causes the website to return a "session expired" error and bringing you back to the login screen. Logging back in with dev tools open also causes the same result.

Things I've tried:

  • Different browsers (Edge, Firefox, Brave)
  • Keeping the developer tools in a popup (in case the site is looking for a resize event)
  • Opening dev tools before opening the site
  • Turning off javascript (site refuses to work, defeats the purpose)
  • Mobile browser debugging
  • Looking for chrome extensions to bypass (didn't find any)

This site presents some security concerns if they are trying this hard to block the use of even the console. The only solution that I can think of is making a custom chrome build without whatever API this site is using to block the use of developer tools.

Steffsh
  • 51
  • 1
  • 2
  • 3
    The front page of the site doesn't block devtools here. Anyway, you can open devtools before the site has a chance to detect it via `chrome://inspect` -> Pages -> "pause". Then you can debug the site's code that tries to [detect devtools](https://stackoverflow.com/questions/7798748/find-out-whether-chrome-console-is-open). – wOxxOm May 11 '20 at 09:41
  • Pausing the site causes the log you out and return the "session expired" error as well. – Steffsh May 11 '20 at 09:49
  • It seems "pausing the site" doesn't mean the same thing I mentioned in my comment which meant you use the exact sequence of steps to open devtools in paused state and use its debugger to find and defuse the code that detects devtools. – wOxxOm May 11 '20 at 10:15
  • I understand what you meant, I should have explained myself better, the site deletes all of its content expect for the HTML code referring to the loading animation which it does when it logs out. And then when I unpause I get the error. – Steffsh May 11 '20 at 10:53
  • Well, my point was that you should use the paused mode to find the code that does all that... – wOxxOm May 11 '20 at 10:56
  • Pausing deletes all of the sites contents – Steffsh May 11 '20 at 12:45
  • Pausing (if done as suggested) can't do anything by itself because the page code can't run. The idea of pausing is to inspect the code in debugger and find the part that does all the bad things. This is not an automatic process. – wOxxOm May 11 '20 at 12:48
  • I swear I'm not dumb but I've followed your steps exactly and pausing the page deletes all of the contents, this doesn't happen on any other site. I have a feeling its a feature and that it's been done on purpose. Thanks for your help though. – Steffsh May 11 '20 at 13:21
  • Well, some things just physically can't happen unless there's something else at play like maybe you have an extension that does something when devtools is opened. As I said, none of this happens here when I open the site and devtools. – wOxxOm May 11 '20 at 13:28
  • It only happens when you're logged in to the site. I've tried your technique on my profile, a profile with no extensions and incognito mode, so I would say chrome extensions are out of the question here. I'm also at a loss at how this site is pulling this off. – Steffsh May 11 '20 at 13:43
  • I'm not registered there so I can't verify but assuming you really did follow the instruction correctly the only other explanation is that it's a bug in the browser. – wOxxOm May 11 '20 at 13:49

0 Answers0