That is just incorrect and sounds like you've been bull<profanity>ted by that community member.
The only connectivity it has is with localhost, one is a TCP connection on 43001 (to control cockpit inputs) and the other is UDP on 43002 (to get readings of the map position for coordinate capture). It listening for UDP broadcasts is likely the reason the heuristic is incorrectly identifying it as trojan. This has also happened with earlier releases.
I have since submitted RC13 with Microsoft to ensure it's no longer producing a false positive. If it still does for you, make sure to update you windows defender definitions to solve that.