Malware Detected in CoreFtpLite.exe (32bit) Installer

davidavoigt · Post by **davidavoigt** » Thu Feb 11, 2016 12:51 pm

I've attempted to download this on multiple PCs/browsers and the latest installer keeps getting flagged as containing malware:
Trojan: Win32/Varpes.M!plock

It is also flagging the CoreFTPLite.msi with the same malware.

Is anyone else seeing this?

Post by **ForumAdmin** » Mon Feb 15, 2016 6:41 pm

Which security software is detecting it as malware?

davidavoigt · Post by **davidavoigt** » Mon Feb 15, 2016 6:44 pm

[quote="ForumAdmin"]Which security software is detecting it as malware?[/quote]

Both Microsoft products:

On Windows 10: Microsoft Windows Defender.

On Windows 7: Microsoft System Center Endpoint Protection

Post by **ForumAdmin** » Wed Feb 17, 2016 2:28 pm

Not having any luck detecting the virus. Is the install downloaded from coreftp.com and have you tried installing outside of your network?

davidavoigt · Post by **davidavoigt** » Wed Feb 17, 2016 4:33 pm

[quote="ForumAdmin"]Not having any luck detecting the virus. Is the install downloaded from coreftp.com and have you tried installing outside of your network?[/quote]

Yes - definitely downloading from CoreFtp.com. I've tried both on my home PC, outside of corporate network - there it gets detected by Windows Defender.

On the corporate network it gets detected by Microsoft Security Essentials.

As of this post, it is no longer getting flagged. Perhaps a definition update resolved it.

davidavoigt · Post by **davidavoigt** » Thu Feb 18, 2016 12:29 pm

Now on 2/18/16, it is getting flagged again as malware (Win32/Varpes.M!plock). Occurring both within corporate domain, and on standalone home PC.

Post by **ForumAdmin** » Thu Feb 18, 2016 5:39 pm

Yes it does appear to flag it as a virus with the latest definitions. The issue has been reported to Microsoft.

Post by **ForumAdmin** » Fri Feb 19, 2016 3:30 pm

Microsoft said the latest definitions will fix the issue. Downloaded the 1.213.6660.0 definitions from today but they did not seem to fix the issue. Waiting on Microsoft now again for a response.

Tested newer updates through version 1.213.6668.0 with the same results - still not fixed.

Post by **ForumAdmin** » Mon Feb 22, 2016 5:26 pm

Relieved to announce that the 1.213.6863.0 definitions on 2/22/16 seem to have resolved the issue.