bramdejager / spcb

The SharePoint Client Browser (SPCB) uses the CSOM to connect to a remote SharePoint site collection and shows the site structure with related properties and values.
GNU General Public License v2.0
174 stars 48 forks source link

SharePoint Online Client Browser v2.1 SPCB.exe infected? #44

Closed bramdejager closed 6 years ago

bramdejager commented 6 years ago

May be a false positive but AVG is detecting Luhe.Fiha.A infection in "SPCB.exe" file of SharePoint Online Client Browser v2.1. Only this .exe seems to be affected. SharePoint 2013 Client Browser v1.8 "SPCB.exe" does not seem to have a problem.

This work item was migrated from CodePlex

CodePlex work item ID: '65111' Assigned to: 'BdeJager' Vote count: '2'

bramdejager commented 6 years ago

[BdeJager@17-3-2016] Hi, sorry to hear that SPCB is seem as a virus... I can assure you that this is not the case. You can validate the sources on what the tool is doing. Maybe AVG have updated the virus definitions and this is causing the detection of SPCB as a virus. Maybe you can exclude the SPCB.exe file to continue working with SPCB.

bramdejager commented 6 years ago

[UnknownUser@17-1-2017]

bramdejager commented 6 years ago

[Sharepointcynic@17-1-2017] The latest release of the SPCB online (3.0) is being blocked due to virus detection. Please advise.

bramdejager commented 6 years ago

[BdeJager@18-1-2017] The easiest workaround is to exclude the file from the AVG scan. Checkout How to exclude files, folders or websites from AVG scanning.

bramdejager commented 6 years ago

[BdeJager@31-1-2017] I did some testing with new builds of SPCB.exe and it seems that it is solved. Not sure why and what caused it to be picked up by virus programs?

On another desktop the anti-virus program picked up the release of SPCB.exe v3.0. The file was instantly removed from the file system after extracting from the ZIP file. After rebuilding the tool and dropping the ZIP with SPCB.exe v3.1 on the same desktop the anti-virus program did not recognize SPCB.exe as a virus and the file was not deleted.

So, completely unclear what caused it. But it seems to be resolved with a new release.

Please let me know if this behavior is the same for you?