A patch is recognized as virus

We've recently started migrating some helpful support documents here: https://github.com/Adobe-CEP/Getting-Started-guides/tree/master/Submit%20Review%20Monetize (this is still very much a work in progress).

Currently, the process for capturing upload errors is the following. This isn't specific to your virus issue but following these steps to document it will help:

How can I fix a server error encountered on the Exchange portal?

Answer: Kindly clear the cache and cookies (at least the adobe.com cookies) before logging into the Exchange Developer Portal. If the issue persists, then please follow these steps:

1. Clear the browser cache and cookies.
2. Log out from the Exchange Portal and log in again.
3. Use the steps below to collect the browser network and console logs as you try to publish your listing.
4. How to capture browser network and console logs:

• Open the Chrome browser and reproduce the error.
• Open the Chrome Developer Tools by typing Cmd+Option+I on Mac or F12 on Windows.
• Please keep the Developer Tools open to see the error.
• Select the Network tab. In the Name column and click on the Name for which you are getting server errors.
• Share all the details that appear in the Headers tab (Request URL, Response Header, Request Headers etc.)
• Next, select the Console tab and share the logs if you see any errors there.
• Create a HAR file by following the steps in this article: https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting
• Kindly share both the network logs and the HAR file through Google Drive or Dropbox.
• If possible, record a video and share it as well, via link or in the same Google Drive or Dropbox folder.

5. Share the logs described above with us (share the logs in the HAR file along with screenshot of network/console logs with ccintrev@adobe.com. Providing logs (and optionally video) will help the Adobe Engineering team in fixing the problem expeditiously.

Just a simple suggestion, did you introduce any new files that were added in the patch? If yes then one of these files should be the culprit. In the meanwhile, lets hope if @erinferinferinf could help us with this issue.

-Manan