McAfee treats preprocessor.exe as a threat

[StOneDOes]

My McAfee Virus Scan treats preprocessor.exe as a threat.

I know this isn't an actual bug with the engine, but I just thought it was worth putting this on your radar:

[reepblue]

The source code is available for the preprocessor. If you feel like investigating, you can #if 0 out most of the code and slowly re-enable things until you get a hit. 

I'm not sure what's causing the false positive, it might detect it's generating code? We don't seem to be doing anything suspicious as far as I can tell. 

 

[StOneDOes]

I'm no expert in this kind of stuff, but I think there's a fair chance that you're right. I've written programs before that generate code and had no issue, but it could be some very specific pattern.

I didn't mean to raise any alarm here; it was more just to make you guys aware so that perhaps it could be somehow rectified before it makes any new users concerned. The executable can be submitted to McAfee for further investigation so they can whitelist (?) it.

[Josh]

That’s very interesting. I stopped using UPX for this reason. I may be able to avoid false positives with a software signature.

[reepblue]

13 minutes ago, Josh said:

That’s very interesting. I stopped using UPX for this reason. I may be able to avoid false positives with a software signature.

Maybe next time before you ship an executable, run it pass Virus Total. This is what I do when I'm not sure about something.

Speaking of which, in my own libraries, I was running into Windows Defender thinking the code I made was a trojan. I think I was trying to make a console logger or something.

[Josh]

Preprocessor no longer in use!