by hazebooth on 8/1/23, 7:35 PM with 51 comments
by 8chanAnon on 8/1/23, 8:29 PM
The reason for the websocket is that the browser console is also rendered inoperable due to the debugger statements and console clear commands emanating from the website JS. A websocket is then the only way to transfer actionable information (such as a password or a secret link). It's not an easy or quick process but, by inserting websocket calls in interesting places, it is possible to figure out what the JS is doing. It also helps a lot to prettify the JS in order to study it. There are websites that can do that for you. Unfortunately, the prettification of the JS may break it so you're still stuck with doing the modifications in the original JS.
I built my own proxy server for this task but I imagine that the same may be possible with a tool like HTTP Toolkit but that means getting the Pro version.
by jkingsman on 8/1/23, 9:50 PM
Example: https://i.imgur.com/BsphnEu.png
by gmerc on 8/1/23, 10:44 PM
by TYT on 8/2/23, 1:19 AM
by rasz on 8/2/23, 9:14 AM
heavy handed approach. I have some moderate success intercepting setInterval/setTimeout and manually sifting to find that one call that starts the ball rolling. Things get old fast when the code you are looking at looks like
0[_0x199d1e(0x815*-0x2+0x1735+0x13f*-0x5)](_0x199d1e(0x3b3*0xa+0x1c1+-0x260d),_0x199d1e(0x2149*0x1+0x9f7+0x1*-0x29f5)))[_0x
by 29ebJCyy on 8/2/23, 5:46 AM
by crazygringo on 8/1/23, 9:56 PM
Could somebody here explain what that means, since the article doesn't? What's a debugger loop? What is the actual JavaScript code that somehow prevents debugging, and how does it accomplish that?
by badrabbit on 8/2/23, 4:05 AM
by 38 on 8/2/23, 12:13 AM
by lini on 8/1/23, 9:35 PM
by ezekiel68 on 8/2/23, 4:46 AM