Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Micosoft Defender Detects Flowkeeper as Trojan:Script/Wacatac.H!ml #107

Closed
titusz opened this issue Jan 24, 2025 · 7 comments
Closed

Micosoft Defender Detects Flowkeeper as Trojan:Script/Wacatac.H!ml #107

titusz opened this issue Jan 24, 2025 · 7 comments

Comments

@titusz
Copy link

titusz commented Jan 24, 2025

Windows flags and removes Flowkeeper.exe as Trojan:Script/Wacatac.H!ml.

@co-stig
Copy link
Contributor

co-stig commented Jan 25, 2025

Hello @titusz, thanks for the report! I can confirm that part of the Windows release pipeline scans Flowkeeper.exe and setup.exe with Windows Defender exactly to avoid issues like this. But it seems that this process is not 100% bullet-proof. Could you please provide a bit more details:

  1. What file do you try to execute? Is it the latest Flowkeeper.exe from the "official" website Downloads section?
  2. What is your Windows version?

In the meantime I will submit those EXE files to Microsoft Security for validation, just in case.

@co-stig
Copy link
Contributor

co-stig commented Jan 25, 2025

Just received an update from Microsoft -- they analyzed both EXE files and concluded that they are safe:
Image
Image

Still, it would be great to get more details from your side, just to be able to reproduce the same issue. Thanks!

@co-stig
Copy link
Contributor

co-stig commented Jan 31, 2025

Got another report like this, after submitting false detection to Microsoft :( Tried with the latest Windows Server VM in EC2 -- all works fine

Image

@co-stig
Copy link
Contributor

co-stig commented Jan 31, 2025

Just installed 24H2, works fine out of the box:

Image

Upgraded with the latest updates -- still works fine:

Image

Installed 2025 Cumulative Update Preview -- still works fine:

Image

Installed all "normal" updates on a 22H2 instance -- works fine there:

Image

Installed preview updates on 22H2 -- still works:

Image

Also ran Defender scans (Quick, Manual and offline) on both systems explicitly -- no threats detected.

@co-stig
Copy link
Contributor

co-stig commented Jan 31, 2025

Alright, I was able to reproduce it by submitting the extracted Flowkeeper.exe to the latest Defender: https://www.virustotal.com/gui/file/07a82b4bc7fd6b049a77f65ef627b248638320ed6c8a9f9ced53072647b71d3a

Already contacted Microsoft and other vendors to mark it as a false positive. Will need to think about how to avoid this for the future versions.

@co-stig
Copy link
Contributor

co-stig commented Feb 3, 2025

Update -- Microsoft removed it as false positive, took them three days. Apparently they don't process those tickets on weekends.

@co-stig
Copy link
Contributor

co-stig commented Feb 3, 2025

I will close this issue, but will certainly do a follow-up, because this is simply not sustainable -- I can't spend days submitting those Windows binaries to all antivirus vendors as false positives for each new release. As a follow-up I created a few other issues:

@co-stig co-stig closed this as completed Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants