Judging by "ReferenceError: webkitRTCPeerConnection is not defined" message in my browser it probably uses WebRTC to get your local IP subnet. I installed an add-on to block WebRTC after I watched a presentation on this tool [1][2] and I recommend you also do this, unless you actively use WebRTC (and don't want the hassle of toggling a switch).
Unfortunately the protocol is vulnerable by design. :(
[1] https://portswigger.net/daily-swig/new-tool-enables-dns-rebi...
[2] https://www.blackhat.com/asia-19/arsenal/schedule/#redtunnel...
replies(1):