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.
deleted by creator
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.
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.
So, the “[edit:
last] previous update” was built fromac41318, 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 🤣
They could be away and not checking on things until they get back.
Or potentially their github account was taken over somehow.
Seems strange that the dev seems to be keeping quiet on this, no?
Which one? The repo owner certainly doesn’t seem very active in general.
