BlockTheSpot compromised or false positive? (github.com)

submitted 2 weeks ago by DoctorButts@kbin.melroy.org to c/piracy@lemmy.dbzer0.com

13 comments fedilink hide all child comments

Seems strange that the dev seems to be keeping quiet on this, no? I'm not telling you to read every comment of every post, you can just skim the post titles. Then you'll see multiple open issues and a few closed issues too going back 5 days to the latest BtS update.

Though I haven't followed this project long enough to tell if this is just the way they normally behave.

Edit:

I'm back at my computer, so it's easier to edit and add info now.

Some key points that have stuck out to me:

Previous version released in July only triggers 2 detections on Windows defender versus 29 for the most recent version: https://i.imgur.com/GIoH7eG.png
Users getting constantly pestered to update to the latest version: https://i.imgur.com/Oege3kU.png
Yeah, naturally, the dev is going to say it's a false positive. Obviously. I've only mentioned that the dev has previously responded because some people barely skimmed through the issues and thought the dev simply hadn't seen the latest open issue from only a few hours ago, when that is not the case.

all 16 comments

sorted by: hot top controversial new old

[-] ReversalHatchery@beehaw.org 18 points 2 weeks ago

Seems strange that the dev seems to be keeping quiet on this, no?

the issue was just posted 7 hours ago. maybe they just haven't seen it yet.

someone in issue #573 asked if the dpapi file is really needed, and by looking at the manual installation instructions, yes, because that contains all the code.

the developer loads custom code into the spotify process by using such an "override" dll file. it works because spotify is voluntarily loading a dll with this name, and if there's such a file in the directory besides the .exe file, it'll take precedence over the original file installed in the system.
the trojan warning is probably triggered because this technique is often used by malware to change the behaviour of your programs, but as with most technologies, it has good uses too

[-] DoctorButts@kbin.melroy.org 0 points 2 weeks ago

the issue was just posted 7 hours ago. maybe they just haven't seen it yet.

There are multiple posts going back 5 days of people asking about it. Check closed issues too, the dev even responded to some of them by saying it's only a false positive.

[+] lol@discuss.tchncs.de 19 points 2 weeks ago* (last edited 2 weeks ago)

[deleted]

[-] N0x0n@lemmy.ml 0 points 2 weeks ago* (last edited 2 weeks ago)

Not the whole code but only the part that triggers those flags. Not everyone is versed in C to "verify the code" himself... That's a stupid take, It's like saying to a toddler to change his diapers on his own when it's dirty.

Strangely enough It went from 1 trigger to 29 triggers after 1 update? Seems rather sketchy :/ In the past (pirated games/software) I would have ignored those warnings and add an exception into my firewall... But nowadays with all the crypto schemes and obfuscated code, I won't go near anything like that.

[-] DoctorButts@kbin.melroy.org -2 points 2 weeks ago

What else are you expecting them to do then if they already answered? Write an essay on DLL injection and walk everyone through the code line by line to convince them it's not malicious?

I said that to indicate that the dev had already responded to the posts, and they were not in a different time zone or on vacation, as you suggested in another comment.

[-] Scary_le_Poo@beehaw.org 4 points 2 weeks ago

It's a dll injection. Of course it gets flagged as a virus, because technically it is. That doesn't mean that it is malicious.

Here is an example... On paper, reshade is a horrifically dangerous piece of software. It doesn't get flagged only because it is well known and virus scanners have an exception for it.

Any of these geniuses stopped to think that Spotify changing its code and altering the way that it interacts with the dll could result in more "detections"?

[-] hendrik@palaver.p3x.de 3 points 2 weeks ago* (last edited 2 weeks ago)

I wouldn't download / update until this gets resolved. Or maybe look for alternatives, or compile/build it yourself. It doesn't necessarily mean it's the developers fault. Could be something else. But maybe don't download something that might contain a Trojan.

[-] Telorand@reddthat.com 3 points 2 weeks ago

Looks like the previous version only had two positive hits on VirusTotal, according to comments, whereas this newest version has 29.

Some said the previous version is still available. I don't really have skin in the game, so nobody should take my advice without doing your due diligence.

[-] fl42v@lemmy.ml 2 points 2 weeks ago* (last edited 2 weeks ago)

So, the "[edit: ~~last~~] previous update" was built from ac41318, since then there were exactly 2 commits:

Both do not immediately look malicious. So, either the release is poisoned (in which case you can build it from source and see if still detected), or the repo was poisoned before, and the payload didn't activate until those changes, or AVs decided to crackdown on random shit running their code in other law-abiding processes' address space 🤣