Here you go.
I uploaded to a few places
ufile
nofile
cheers
Maybe? a tip? But not needed or necesary! Tip the dev better.
B8zNWAJiQ5AEVdLZJDZfiQ2WDxYy72w1RG
Windows Defender detecting trojan in 64bit version. I did not bother with the others after that...
But as always. It's good to check files. And if there is any risk at all I suggest you don't use the links I posted.
I don't know what to tell you. Windows Defender seemed to find a legit threat. I built 32 and 64 myself and they did not have any issues with AV.
ok. I have been doing a test on my end. I find this very interesting I went and ran a scan on the original compiled files. The 32 bit version had no threats detected by windows defender. the 64 bit version on the other hand did. I should have tested before but usually windows had a popup telling me there is/was a threat and it did not pop up. I had to manually scan them. Also, i used a hashing app to hash the files. I could not has the 64 bit version because it would detect said trojan. So i appologies for posting the 64 bit build. The 64 bit build seems to be infected. Now i am not sure if its real or a false positive but it does seem to come up as dirty. I don't know why but that is what was built in vs2013 when i select 64 bit.
I am currently rebuilding the source and will report back when done. I still am not sure what exactly happened or if its even a real hit. But fo rthe time being the 64bit build should be avoided.
Also here are the hashes for the 32 bit build which scans clean on windows defender
md5 795B7F9693A98FF568E1AE0EBC5D9C7F
Sha-1 2084EE0EA845F64B5001F1F3ED26B67BC69ED0D8
Sha256 30ABBDC0DF8538E417534A5A49E24975D2F00DC9BFDCD0A8B8142AE1A7D1A5B1
Sha512 7D9B99CDF7DC3987038FA0D66969186BABA82757864B9F637954BA5716B03ABF87B9D3AA2FAEF16 744594EFDAF1FC3F21D01132F3B52ACD179D5E58B9D2F955E
Used quickhash