3 ms·

Try Anti-Anti-Debug [0]. It's a simple extension to bypass those kinds of anti-debugging techniques. Made it in a few hours a while ago for similar reasons. 0:

• rand846633 3y ago
  Than you for this valuable tool; Looking forward to using it!
• irrational 3y ago
  Can you make one for Firefox too? ;-)
  • Andrews54757 3y ago
    it's a simple script, should be portable to firefox with minor modifications. The source code is available on Github [0]. 0: https://github.com/Andrews54757/Anti-Anti-Debug https://github.com/Andrews54757/Anti-Anti-Debug
    • rasz 3y ago
      This is great. I was wondering why does it disable console.table, but then I went to one of my favorite shady sites I screw around with from time to time (I intercept and patch setTimeout/setInterval to disable particular function doing constant debug() injection), lo and behold tables dates and big arrays (not yet covered by your tool) spamming in console :o slowing down devtools window to a crawl. For console.clear I have this window.console.clear = function clear() {console.log(clear.caller, "Asshole script called console.clear()")} hoping I get a glimpse of what exactly is calling it.
    • elashri 3y ago
      I don't think this will work out-of-the-box in Firefox. Firefox handles the console object differently than Chrome, especially when it comes to the console.clear() method. In Firefox, when a console is cleared, it's not just the display that's cleared. The entire console object is reset. This means that any modifications made to the console object, such as redefining console.clear(), are lost when console.clear() is called. You can try this on this demo [1] website that uses devtools-detector library [2] [1] https://blog.aepkill.com/demos/devtools-detector/ https://blog.aepkill.com/demos/devtools-detector/ [2] https://github.com/AEPKILL/devtools-detector https://github.com/AEPKILL/devtools-detector