Unity standalone build triggers McAfee malware detection

Hello André,

Let me clarify your questions.

Certainly we know about it as this has happened before and we are monitoring the situation. Actually, this is a problem any software development environment is exposed to as Anti-virus detections are known to be more aggressive and have False Positives specially with unseen, unsigned, new binaries such as those part of the build process.

We are aware of the problem and we will take further action by adding documentation and guidance, and looking for more generic solutions together with the Anti-virus vendors.

Yes, it is possible. How likely will depend on how effective the Anti-virus vendors can fix this problem based on our input and options. And let me state, this problem can happen with any binary at any time, Unity or other as it relies on the Anti-virus detection logic.

Now, how do you fix the problem you stated. We have three options.

First, share with us the file names and the SHA-1 of the detected Unity binaries so we can uniquely identify them and submit those to McAfee as False Positives.

Second, if this issue blocks your development. You may exclude the folders where those files are detected from the Anti-virus scanner. However, this can potentially reduce your protection, hence assume it as a short-term fix only and remove the exclusion later on once the problem does not reproduce.

Third, if you feel uncertain this would actually be a real malware infection. You may submit these files directly from your system to McAfee as False Positives https://kc.mcafee.com/corporate/index?page=content&id=KB85567 . Taking into account those files should not be private, sensitive or under any special NDA as it will be shared with a third party for analysis, the Anti-virus vendor.