Jacob

Not exactly sure what's causing this, but I solved it by using dynamic imports for the miragejs module. `const { createServer, Model } = await import("miragejs");` The above is added...

I don't know if this works for you, but if you can access an element within the iframe, you can also programatically append a script into the iFrame. Technically, you...

After thinking about this for a bit, I suppose the correct approach here is to create a whitelist for allowed DNS resolver IPs

I see. I think the approach of blocking all entrypoints to changing the DNS resolver IP (e.g. `dns.setServers`, and `lookup, resolve`) and only allowing resolvers known ahead of time.

This is definitely an approach that I'm going to be pursuing. There is currently a problem with Hagana in that it can't stop pre/postinstall scripts due to them running in...

I'll take a look at this. It should work

Interesting, I tested for a similar case where I checked if: `const {execSync} = require("child_process")` bypasses the protection (it doesn't), but seems that using import bypasses the protection.

This is weird, it's only happening to me occasionally. Do you mind upload a repo with your project structure?

But won't the initial overrides already have taken place?

🤦🏻‍♂️ This is a good find. I guess the only way to solve this is by maintaining internal state to know that hagana has already been required and then prevent...