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
Trojan Crypt in Spytify? #278
Comments
I went and read about this kind of alert:https://www.spywareremove.com/removetrojancrypt.html I can confirm this is a false positive Spytify does not do that. The only web browser page it opens is when you are using spotify api, we ask you to log in into your account to authorize spytify api to use your account to search for metadata of the current song that is being played, since spotify api is private and the app does not come with it's own client id for spotify. there are also buttons on the UI that links to the project website. |
so I found out a bit more information, I found out that using prevent to sleep is seen has a trojan, spytify tells the system to not go to sleep until the recording session is done, and it does not like that. see with powershell as admin, that spytify gets attached to events: after adding some more code to spytify recently, I added what microsoft recommanded for media recorders and use
After adding this mode, I now see on my tests machines that the app is now completly deleted on execution and it's falsy flagged as a
https://malwarefixes.com/threats/trojanwin32-wacatac-dml/ what I did is that I removed that commit, so the recorder becomes less effective when away from keyboard, but I cannot removed PreventToSleep completely otherwise it compromises the recorder, as soon as the computer comes back from sleep the recorder will resume and add all the wave buffer (spotify continued to play) into one file |
…riggers anti virus windows defender falsy detects the app as a Win32/Wacatac.G!ml https://malwarefixes.com/threats/trojanwin32-wacatac-dml/ related to #278
Hi all, I was just given a notification of a trojan crypt hidden in spytify. I am no computer expert, just wanted to make sure spytify didn't make an accidental pull request that should have not happened.
The text was updated successfully, but these errors were encountered: