Windows 10: Found Threat at My Windows Defender Trojan:BAT/PS.Runner.VS!MSR . How to fix it?

I'm using Farbar Recovery Tools and this is my FSRT and AdditionalFRST.txtAddition.txtThanks in Advance

:)

 

Trojan-PoweLike!bat

Defender is not finding and removing or quarintining a malware "Trojan-PoweLike!bat" that I can not get off my computer. It was detected by Stinger, but it keeps coming back. Windows defender is not finding it How can I completely remove it????

 

Windows defender false positive - forced to allow threat

Windows defender has started to identify C:\Windows\System32\mshta.exe as a threat [normally reported as a Trojan Powessere.G]. I use mshta.exe to run an hta custom MsgBox - I have been hoping to keep using my current CustomMsgBox tool [batch file calling a vbs-hta file] until later this year when I hope to have had enough time to replace it with a PowerShell alternative.

Windows defender's notification lets me "allow the threat" but that seems to me to be a bigger security hole than is necessary - it will now ignore a potentially real intrusion when all I want to run is a genuine Windows component. My immediate problem is fixed but I would prefer to fix the false positive using the exclusions list.

I cleared the 'Allowed threats history' so I could use the exclusions list instead. I added C:\Windows\System32\mshta.exe to the file exclusions list and I checked that it had taken properly by checking the exclusions list both in the UI & in the Registry. But the exclusion made no difference, it continued to detect and block the exe.

I have repeated the attempt several times [by clearing the allowed threats list & exclusions list beforehand] and the results are the same every time
- allowing the threat works,
- using the exclusions list has no effect.

I studied the relevant tutorial but have not spotted an error in what I have been doing - Add or Remove Windows Defender Exclusions

Does anybody with experience of using the exclusions list to counter false positives have any suggestions for me?

Denis

 

Trojan Found and Deleted....but it Returns (Trojan: HTML/Phish.AB!MSR)

Windows defender periodically finds a Trojan in a .htm file in my Windows Communications appdata area (see attachment). You will notice that the file is in the Attachments folder. Windows defender seems to delete this threat but after a few days or a couple
weeks, the threat will return in the exact same location.

I have no evidence that the Trojan is actually running on my computer. I believe it is just sitting in the file waiting to be executed. I have not knowingly run this file and am usually careful about phishing attacks.

Only Microsoft Defender will find it. I tried using Malwarebytes, Bitdefender and Microsoft Safety Scanner. None of these even finds it.

MS-Defender says that it is successful at removing it and a scan immediately after the clean will not find the Trojan.

A few troubleshooting actions to date:

• Have removed the threat and immediately opened all known Microsoft communications programs (Outlook, Windows Calendar/Mail, Skype, Skype-Biz, Teams). I then reran a scan but did not find the Trojan. Nevertheless, it did return a couple weeks later.
• I have started my computer in Safe Mode and deleted the entire package folder. After rebooting, the Trojan is no longer found by Defender. However, the folder and its content is eventually recreated along with the Trojan threat.
• I had a case opened at Microsoft (who more-or-less had me repeat everything I had already done). MS ultimately recommended that I rebuild/refresh my entire computer. I am not adverse to doing this but I am worried that since the Trojan appears to be in
  an attachment within Windows communications, it will simply return. I do not want to waste my time.

I currently run a daily scan of the appdata\package folder so that I can identify when the file returns.

MS-Surface Pro i7/16GB/512GB with all Windows 10 Pro updates completed.

Office 365 environment with most all files stored in OneDrive or SharePoint.

Thank you for any further thoughts on this issue.

-bs