-
Notifications
You must be signed in to change notification settings - Fork 543
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
snoretoast-x86.exe detected as a trojan by McAfee Endpoint Security #848
Comments
YouTube-Music-1.18.0.exe Also detected in Virus total website scanned by Trend micro ( https://www.virustotal.com/gui/file/f64aa95b6778a61cf9e50f6f4b8d28fc64fe08980c4ded44b48f8a0420e6622f?nocache=1 ) |
Hey folks, that seems weird indeed 🤔 Snoretoast is compiled from source in the repo (also applying a missing patch along the way) and nothing was changed recently in that area, not sure why some antiviruses suddenly detect it (false positive?) - if you prefer, you can compile it yourself by setting up the repo (cloning and install dependencies with yarn) then building snoretoast (see the linked CI file for instructions - it consists in cloning the repo, applying the patch then compiling it), then building the app ( |
@th-ch seems like some changes were made and a new snoretoast version was released KDE/snoretoast@8502ef0 (this is pretty much what the local patch does) https://binary-factory.kde.org/job/SnoreToast_Release_win64/ might work with the signed file now, need some testing (I cannot test it sadly)
|
Reinstalled today, and McAfee did not protest. |
New snoretoast version was officialy released https://download.kde.org/stable/snoretoast/0.9.0/ edit: the new version didn't actually fix the bug |
Whether or not snoretoast-x86.exe is malware, this creates a poor user experience, and compromises trust with this repo.
McAfee ENS detects the following file as a trojan (RDN/Generic.dx):
%userprofile%\AppData\Local\Temp\nsoBF47.tmp\7z-out\resources\app.asar.unpacked\node_modules\note-notifier\vendor\snore\snoretoast-x86.exe
The text was updated successfully, but these errors were encountered: