OpenLogi.exe blocked but shouldn't be flagged as a dangerous file
Hi,
I'm using OpenLogi, an open-source software allowing personnalisation of Logitech products without the hassle of their official app.
The full project is stored in GitHub:
The official app from Logitech uses more RAM than needed, is unnecessarily big, and requests an account to personnalise products, hence why OpenLogi exists and become more and more popular.
While updating the software today, I noticed FS Protection (version 26.9 beta 3) flagged the executable file as a dangerous file and did move it to quarantine.
I want to report this as I believe this is a false positive and could be tweaked.
Best regards,
Melvin
Answers
-
Hello,
They usually recommend using this webpage for submission: https://www.f-secure.com/en/support/submit-a-sample
There used to be a feature for sending files directly from quarantine (or so), but it was likely dropped at some point and never brought back (as for yet).
What is detection name, by the way? Is it something like: TR/W32.Malware or TR/W64.Evo;
Or a more specific detection name?
I mean, since it is recently updated (or even while updating itself) - it may be just too "fresh" and "unknown" for F-Secure Security Cloud or any engine in use. Therefore, detection can be even simply temporary, based on certain indicators and an insufficient reputation score. In other words, the detection might disappear on its own following a "re-analysis" in the backend.
Thanks!
-
Essentially, the behavior of the program is what triggered the quarantine. Not necessarily the program itself. In my experience building custom pipelines, running Python scripts frequently triggers antivirus software to quarantine files. This doesn’t mean the script is dangerous—it’s flagged because of its behavioral footprint. Many tools, especially open-source utilities, rely on chained operations where multiple processes interact with a single file (for instance, an audio pipeline that splits a long file, streams the chunks to a transcription API, and stitches the results together). To keep things organized, these scripts routinely write intermediate files to hidden temp directories. Because that exact sequence—rapid temp-file creation, external network calls, and unsigned process execution—mirrors common malware techniques, the antivirus steps in as a precaution and slams the brakes on the process.
