Minato_Namikaze wrote

Bashful wrote I'll take a look at the source and let you know ;P
Edit:
Not really sure.
Honestly, a lot of .NET exe's seem to have false positives when internet connectivity is involved with the program. Didn't really see any class that specifically caught my eye however.


Did you mention using a .dll? If the .exe was bound with the dll or the executable was obfuscated, that could be why.

There is no obfuscation, but I did merge two open-source DLL files so maybe it has something to do with that.

Probably. Binding files is a popular method for virus spreading, so generic bound files could throw off a red flag