This was most likely caused by an oversight on our end. We've enabled file signing in-engine, so the next build should hopefully be less susceptible to being wrongly flagged by antivirus software.
thanks
