github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #666] virus warning in latest Windows version #528

New issue

Closed

opened 2026-05-05 06:36:09 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 06:36:09 -06:00

Owner

Originally created by @rebroad on GitHub (May 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/666

Originally created by @rebroad on GitHub (May 12, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/666 ![image](https://user-images.githubusercontent.com/1530283/81645031-6c695a80-945b-11ea-870b-bcec560f699b.png)

gitea-mirror

2026-05-05 06:36:09 -06:00

closed this issue
added the
windows

wontfix
labels

gitea-mirror commented

2026-05-05 06:36:17 -06:00

Author

Owner

@simons-public commented on GitHub (May 12, 2020):

@rebroad Do you get the same results if you compile it yourself or is this only on the 2.3.2 release installer?

@simons-public commented on GitHub (May 12, 2020): @rebroad Do you get the same results if you compile it yourself or is this only on the 2.3.2 release installer?

gitea-mirror commented

2026-05-05 06:36:20 -06:00

Author

Owner

@simons-public commented on GitHub (May 12, 2020):

@rebroad Anity-AVL flags the Windows version of Barrier even when built on Azure Pipelines (which obviously doesn't add malware). I uploaded the installer and release zip from the latest build artifacts on Azure and got the same detection.

I've been through the source of this project quite throughly and this is most certainly a false positive from whatever heuristics that Anity-AVL lab is using. A lot of the less established AV labs tend to get pretty high false positives.

I see from your profile you have some background with crypto currency so if you're still concerned you can look through the code yourself and confirm that there isn't any code pertaining to crypto mining.

@shymega Unless somebody wants to handle encrypting and sending every release to the false positive contact at Anity this can probably be closed.

@simons-public commented on GitHub (May 12, 2020): @rebroad Anity-AVL flags the Windows version of Barrier even when built on Azure Pipelines (which obviously doesn't add malware). I uploaded the installer and release zip from the [latest build artifacts](https://dev.azure.com/debauchee/Barrier/_build/results?buildId=172&view=artifacts&type=publishedArtifacts) on Azure and got the same detection. <img width="967" alt="Screen Shot 2020-05-12 at 09 16 21" src="https://user-images.githubusercontent.com/35010457/81719046-62cafd00-9431-11ea-94b1-6d9c72e2f8bf.png"> I've been through the source of this project quite throughly and this is most certainly a false positive from whatever heuristics that Anity-AVL lab is using. A lot of the less established AV labs tend to get pretty high false positives. I see from your profile you have some background with crypto currency so if you're still concerned you can look through the code yourself and confirm that there isn't any code pertaining to crypto mining. @shymega Unless somebody wants to handle encrypting and sending every release to the [false positive contact](https://www.antiy.net/contacts/) at Anity this can probably be closed.

gitea-mirror commented

2026-05-05 06:36:24 -06:00

Author

Owner

@shymega commented on GitHub (May 12, 2020):

There's no reference to crypto-currency in the source code, no.. only a few keywords such as XK_CURRENCY as a preprocessor instruction, and the Thai Currency symbol in a comment. Numerous matches for the keyword crypto, but that's to be expected. The keyword coin comes up a few times, for French translations, but nothing that should really be of alarm.

I will have a look at false positive reporting, but I can't promise anything. I don't have full rights to the repo, so I can't necessarily adjust Azure in great depth.. but I can have a play with the CI frameworks in the repo itself.

@shymega commented on GitHub (May 12, 2020): There's no reference to crypto-currency in the source code, no.. only a few keywords such as `XK_CURRENCY` as a preprocessor instruction, and the Thai Currency symbol in a comment. Numerous matches for the keyword `crypto`, but that's to be expected. The keyword `coin` comes up a few times, for French translations, but nothing that should really be of alarm. I will have a look at false positive reporting, but I can't promise anything. I don't have full rights to the repo, so I can't necessarily adjust Azure in great depth.. but I can have a play with the CI frameworks in the repo itself.

gitea-mirror commented

2026-05-05 06:36:27 -06:00

Author

Owner

@shymega commented on GitHub (May 12, 2020):

Looking at Anity before, I can't help but have my doubts about them. Their website isn't encrypted, and it just seems a bit 'off' to me. I would like to get Azure Pipelines to automatically submit, but somehow I think this won't be as effective as a 'human' submitting. Hm. Maybe I'm wrong about Anity.

I suppose the question really is: does this affect the majority of Barrier users, and should we cater for the minority that may use AV software such as Anity, or should we favour the majority?

@shymega commented on GitHub (May 12, 2020): Looking at Anity before, I can't help but have my doubts about them. Their website isn't encrypted, and it just seems a bit 'off' to me. I would like to get Azure Pipelines to automatically submit, but somehow I think this won't be as effective as a 'human' submitting. Hm. Maybe I'm wrong about Anity. I suppose the question really is: does this affect the _majority_ of Barrier users, and should we cater for the minority that may use AV software such as Anity, or should we favour the majority?

gitea-mirror commented

2026-05-05 06:36:30 -06:00

Author

Owner

@simons-public commented on GitHub (May 12, 2020):

I think you're right about Anity. I think if it's addressed as a known issue (like maybe in the wiki) that it shouldn't be a concern for the majority of users. I think most people savvy enough to be seeking something like Barrier will recognize this as a false positive.

@simons-public commented on GitHub (May 12, 2020): I think you're right about Anity. I think if it's addressed as a known issue (like maybe in the wiki) that it shouldn't be a concern for the majority of users. I think most people savvy enough to be seeking something like Barrier will recognize this as a false positive.

gitea-mirror commented

2026-05-05 06:36:34 -06:00

Author

Owner

@shymega commented on GitHub (May 12, 2020):

Agreed. Will add something to the wiki. Bit annoying that Anity sees it as a false positive.. but as you said, lesser-known/smaller AV companies do seem to have a tendency to mark software as malware.

@shymega commented on GitHub (May 12, 2020): Agreed. Will add something to the wiki. Bit annoying that Anity sees it as a false positive.. but as you said, lesser-known/smaller AV companies do seem to have a tendency to mark software as malware.

gitea-mirror commented

2026-05-05 06:36:36 -06:00

Author

Owner

@shymega commented on GitHub (May 12, 2020):

Added an entry to the wiki.

Thanks for bringing this to our attention, closing issue now. 👍

@shymega commented on GitHub (May 12, 2020): Added an [entry](https://github.com/debauchee/barrier/wiki/Known-Issues) to the wiki. Thanks for bringing this to our attention, closing issue now. :+1:

gitea-mirror commented

2026-05-05 06:36:39 -06:00

Author

Owner

@ruevs commented on GitHub (Jun 16, 2020):

Just for reference:
Now McAfee-GW-Edition
also detects https://github.com/debauchee/barrier/releases/download/v2.3.2/BarrierSetup-2.3.2.exe as BehavesLike.Win32.AdwareAdposhel.rc

https://www.virustotal.com/gui/file/a6a195c55c199b35c737d7494327b37da94ded4eb2592871d4ad747aa8baa39a/detection

@ruevs commented on GitHub (Jun 16, 2020): Just for reference: Now `McAfee-GW-Edition` also detects https://github.com/debauchee/barrier/releases/download/v2.3.2/BarrierSetup-2.3.2.exe as `BehavesLike.Win32.AdwareAdposhel.rc` https://www.virustotal.com/gui/file/a6a195c55c199b35c737d7494327b37da94ded4eb2592871d4ad747aa8baa39a/detection

gitea-mirror commented

2026-05-05 06:36:41 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

Unfortunately there's nothing we can do about antivirus vendors flagging Barrier as virus. This is bug in the specific antivirus software, not Barrier.

@p12tic commented on GitHub (Jan 10, 2021): Unfortunately there's nothing we can do about antivirus vendors flagging Barrier as virus. This is bug in the specific antivirus software, not Barrier.

gitea-mirror referenced this issue

2026-05-05 07:58:37 -06:00

[PR #528] [CLOSED] translation: ja-JP #1651