Thanks for letting us know and sorry that you’re running into these issues. It looks like someone is embedding mitmproxy into their software and routing all your traffic through it - definitely not how we want our software to be used. We haven’t heard of this before, and we’d be very interested to find out which software on your machine is doing this. Would you mind hopping on our Slack channel (https://slack.mitmproxy.org/) so that we can help solving this with shorter turnaround times?
If you have gotten to the bottom of this already, I’d appreciate a quick pointer on what software is responsible for this.