-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Virus report in the latest Windows release #945
Comments
One VirusTotal vendor seems to agree (although just one): https://www.virustotal.com/gui/url/4696a209aa804307c7db63664e29cfe374a70c35724577de565d47564175e6c8?nocache=1 |
Thanks, I will look into it but I didn't notice anything wrong in our CI, so I am suspicious of the report. Also, can you try downloading https://github.com/cargo-bins/cargo-binstall/releases/download/v0.22.0/cargo-binstall-aarch64-pc-windows-msvc.zip , the non-full version which doesn't contain the debug symbols and see if it still triggers the anti-virus? |
Yeah I tried that immediately after, and that one triggered as well. I didn't have same issue with previous versions and could build from source ( |
That's strange. Can you unzip the achieve and see which file triggers the virus checker? |
I had a look at the output of |
seems a fairly common false positive for various rust projects, see eg tauri-apps/tauri#2486 |
Tried today, looks like 3 VirusTotal vendors think that Although now I tried on |
That really sounds like a false positive. The I don't think The debug symbols and |
Looks like 0.23 doesn't have this problem, so closing. |
Trying to download latest cargo-binstall from Github (https://github.com/cargo-bins/cargo-binstall/releases/download/v0.22.0/cargo-binstall-x86_64-pc-windows-msvc.full.zip) triggers antivirus on Windows:
This might be a false positive, but worth looking into in case build pipeline got compromised. Defender tends to be pretty good in the last decade or so, and this is literally the first time I got a report from it for a downloaded app in many years, so I don't want to dismiss it prematurely.
The text was updated successfully, but these errors were encountered: