I’m trying to take a look at a scamming website, but it’s using the debugger spamming to make reverse engineering difficult. Is there a way to just disable the debugger keyword? I don’t really like to give the websites control over whatever I want to view.

  • niartenyaw@midwest.social
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    would it help to curl down the source html and scripts? I’m no professional at dealing with malicious code, but i would definitely recommend doing it inside a clean VM or docker container or something

    • tkpersonOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      curl the source down works, but it makes things more complicated. The source code is obfuscated making it incredibly hard to read. This is where using the web debugging tools shine. If I want to figure out which code is trigger what, I can just look at the call stack. I also wanted to look at the internet traffic to see how things work from there. I could intercept all the HTTP requests but that wouldn’t give things like the call stack. I think it would be much easier if there’s a way stopping the debugger spamming trick.

      • niartenyaw@midwest.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        ah ok makes sense. maybe after curling you can delete the debuggers/infinite loops in the scripts and then load all that locally into the browser for the tools? will just need to change the script sources go be your local copies