I am the developer of an email notifier (to add context to the filename) and each release has several distribution packages. Inevitably, one or two are always reported by McAfee-GW-Edition on VirusTotal as BehavesLike.Win32.Suspicious.rc
The above files use NSIS installer (and are digitally signed). The zip distributions, containing the same files, usually pass clean:
Please let me know what I need to do to get a clean bill of health, now and in the future!
Thanks for the link to the related topic. I read through it, and the news is not optimistic considering it's from over a year ago. But let's put that aside as I still have a problem. In that link it referenced 2 possible actions to report a FP:
- which requires "Access to the Web Gateway GUI interface" which I do not have
- which I have used before and I have never gotten a response. I'm not sure if it was the case on previous attempts (earlier this year), but when I tried it a few days ago, I noticed that it didn't even ask for the sample to be uploaded. I went through it again, and I still don't see any field to indicate the sample.
Usually we get the software developer to submit the files but with the nsis installer involved I am loathe to suggest that way as it is above my experience and the posts in the threads to the left (More like this) do not suggest this. I will however ping the tech who did solve 1 user's issue and see if he can visit here.
We're working with the app developers on that signature to see what can be done to avoid this particular false, and still provide the protection it was designed for. It will take some time, since we can't really tackle this one file at a time, so please bear with us.
I assume that by "app developers" you mean the NSIS and/or McAfee-Gateway developers, but I would be happy to help in anyway I can. It would certainly be beneficial to me in the long-run to get this taken care of. And, after all, we are apparently long-lost cousins...
A couple of things to note:
1) I had to build new installs this morning and I just submitted them to VT. The same 2 installations still have a problem:
In case it helps for comparison, I have 2 other NSIS builds that don't have a FP (neither this time nor the previous time, which I didn't mention above):
(for the sake of whitelisting, the hashes referenced in the earlier post are no longer used)
2) I'm using NSIS v2.46 (the last official build), but yesterday I downloaded the latest beta (v3.0b2) for testing purposes only. I had to gut some of the incompatible script just to get quick results. The lines I removed had to do with the capability to run the installer with elevated privileges (which is standard for installers) but allow the installed program itself (at the end of installation) to launch with normal user privileges. I wasn't sure if this would cause a different analysis, but McAfee-GW still came up with the suspicious result.