GSB Forums

False virus detections

admin - 17-10-2017 at 02:51 PM

A number of users report virus detection's on GSB beta install file, enhanced walk forward optimizer and portfolio analysts.
I get the same issues with my autoit scripts and nircmd.exe files. (not related to me)
Here are some fixes that I'm using.
Surprisingly gmail.exe is not flagged. I thought it might be because it sends emails.

The logic is simple. Files like autoit (a scripting language) could be used to do damage, therefore declare all autoit scripts as virus's.
GSB files (not the installer ) are obfuscated to protect them being DE-complied.
Virus are obfuscated, therefore GSB is a virus.
I could submit false detection reports but there are so many virus companies, and GSB currently is getting a few builds a week. The last false positive report I sent was meet with no response by the Chinese vendor.
When we have a stable build, that would be more possible to fix the issue.
Please see a fix below. Basically you can exclude the GSB folder and or exe's.



mse2.png - 66kB mse.png - 78kB

Microsoft security

mindesb - 26-12-2017 at 04:36 AM

Microsoft security essentials reports as virus too. Attached screenshot.

Capture2.PNG - 47kB

admin - 26-12-2017 at 06:54 AM

My posting above was on MSE.
the next release gets 1 out of 66 virus programs showing it as a virus.
Should be uploaded in the next week.
You also ought to run the latest beta. Just note that the file path is wrong and it says file not found.
You need to make a shortcut to gsbstandalone...exe not gsb...b.exe

admin - 20-7-2018 at 04:58 PM

Today microsoft security essentials is flagging and deleted gsb1.0.47, ewfo as have virus.
Nothing has changed in gsb or ewfo to generate this.
At the heart of the issue is GSB files are obfuscated. Virus are obfuscated. Therefore GSB = a virus.
Not good logic. Virustotal.com shows gsb 1.0.47 passing 65 of 67 virus detectors including microsoft!
See steps below to exclude c:\gsb



vt.png - 163kBv1.png - 55kBv2.png - 61kBv3.png - 51kBv4.png - 23kB

JasonT - 31-7-2018 at 08:23 PM

I just had a repeat problem with that after installing the most current build and a BitDefender pattern update. I had trouble getting GSB to reinstall so I had to uninstall, delete the GSB folder, then reboot. I then had to add the installer file to my BitDefender application whitelist to get it to run. I then re-installed GSB selecting the 'launch GSB' check box at the end of the installation (mistake). BitDefender proceeded to delete the GSB executables again. I repeated the process and did not select 'launch GSB' at the end of the install but instead whitelisted all the newly installed GSB executables then ran GSB. Is working fine now.

admin - 1-8-2018 at 06:06 AM

Quote: Originally posted by JasonT  
I just had a repeat problem with that after installing the most current build and a BitDefender pattern update. I had trouble getting GSB to reinstall so I had to uninstall, delete the GSB folder, then reboot. I then had to add the installer file to my BitDefender application whitelist to get it to run. I then re-installed GSB selecting the 'launch GSB' check box at the end of the installation (mistake). BitDefender proceeded to delete the GSB executables again. I repeated the process and did not select 'launch GSB' at the end of the install but instead whitelisted all the newly installed GSB executables then ran GSB. Is working fine now.

Thanks for the tip. GSB is using a temp folder for cloud information which is also giving issues. Fixed in the next beta version to be releasef.