#2781 closed task (upstream)
xpra 4.0 wrongly detected as Trojan:Win32/Sprisky.D!cl
| Reported by: | Antoine Martin | Owned by: | Antoine Martin |
|---|---|---|---|
| Priority: | major | Milestone: | 4.1 |
| Component: | packaging | Version: | 3.0.x |
| Keywords: | Cc: |
Description
Trojan:Win32/Sprisky.D!cl: This detection uses artificial intelligence (AI) to identify new and emerging malware. It is designed to catch threats with varied impact, including banking trojans, botnets, ransomware, cryptominers, and backdoors.
Microsoft, your AI needs work.
Attachments (1)
Change History (4)
Changed 8 months ago by
| Attachment: | trojan-false-positive.png added |
|---|
comment:1 Changed 8 months ago by
| Resolution: | → upstream |
|---|---|
| Status: | new → closed |
The false positive has been reported here: filesubmission.
Not much else we can do.
Users can install the "Client" builds, as those don't have the html5 client.
Funny that it's the html5 client that's triggering it this time.
comment:2 Changed 8 months ago by
Official response:
xpra-python3-x86_64_4.0.1-r26379.zip Submission ID: c525bd8e-01cc-44fb-9a46-ed0804f16fc0 Status: Completed Submitted: May 28, 2020 11:40:53 User Opinion: Incorrect detection Analyst comments: We have removed the detection. Please follow the steps below to clear cached detection and obtain the latest malware definitions.
comment:3 Changed 3 days ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2781
Note: See
TracTickets for help on using
tickets.
copyleft 2010 - 2020
windows defender trying to be smart