I think it's going to be important to recognize and block javascript/wasm by the bytecode it compiles down to. As far as I know we don't have this ability to "

I think it's going to be important to recognize and block javascript/wasm by the bytecode it compiles down to. As far as I know we don't have this ability to "jump into" the process. ublock or umatrix can't be extended to do this currently. You could send the scripts the browser downloads to an outside service for fingerprinting, but doing this in the same browser isn't possible right now. This wouldn't completely stop a server from generating code that compiles to slightly different bytecode. Then the move would be to identify side effects of the execution? Cat and mouse...