The hash has been whitelisted. Could you rescan and check if it still comes up?
We all have problems with this file being detected. Each of us should have a file that has a unique hash value. What other way may exist to prevent McAfee files from being identified as unknown and suspicious?
In the upcoming release of GetSusp - we've hardcoded certain executable filenames/filepaths that tends to be polymorphic on the endpoint. We could add the meta data for this file within the GetSusp logic so that it gets excluded from being reported.
Thanks for letting us know of this.