webhook

JavaScript anti-debugging tool Main problems addressed.. 1. Console-based developer tools detection Some websites use the console to detect whether F12 (developer tools) is open. The extension hooks the console object directly and disables all output to bypass detection. 2. Browser freezing based on pushState Some websites keep inserting things into Chrome's cache, commonly seen on sojson and sites imitating it. This has been disabled. 3. Browser freezing and developer tools detection based on debugger For dynamic debugger statements, the extension hooks Function.protype.constructor and replaces all debugger strings. Debugger constants written directly in JavaScript cannot be hooked (actually they can, but I don't know how to implement it in an extension); you have to right-click and set a conditional breakpoint yourself to bypass them. 4. Code style detection based on regular expressions Detection of whether code has been formatted using regular expressions is disabled. 5. sojson-based anti-debugging For sojsonV5, bypass all anti-debugging with one click. 6. setInterval-based anti-debugging Hooks setInterval so it cannot take effect while retaining its original characteristics, making the hook undetectable. It also alerts you when a function is detected. 7. Cookie-based encryption tracing You know what this is about.. 8. stringify-based hook You know what this is about. When you really can't find an entry point, you can try your luck: plaintext objects are usually converted to strings with stringify before password algorithms or special encryption. 9. Out of laziness, it will keep being improved...