Clipboardy is detected as virus

[Avaruz]

What happened?

When I upgrade to the last version I have this:

Reference Issue closed by owners of clipboardy:
sindresorhus/clipboardy#109

What did you expect to happen?

Upgrade to the last version

Client information

Client Information

Run gemini to enter the interactive CLI, then run the /about command.

> /about
I can't install the gemini-cli

Login information

No response

Anything else we need to know?

No response

[jle-pass]

+1
FYI, an analyst informed me of the presence of obfuscated code with base64 and XOR, hence a classification as Riskware, possibly linked to the compiler used to make the executable programs, but this raises doubts.

[scidomino]

This is a false positive. The anti-virus companies need to update their data.

[pentium10]

This was flagged by Bit Defender as well

[Avaruz]

This is a false positive. The anti-virus companies need to update their data.

Saying it's a false positive doesn't fix issue; one antivirus is fine, but now there are seven, and none of them are unknown antivirus programs.

Why don't they talk to the author and have him review it?

[breun]

@Avaruz The clipboardy maintainers has stated that he considers this a false positive.

[Gr0g33k]

Hello,
Currently, there are more than 20 antivirus programmes, including Google, that consider Clipboardy to be malicious on VirusTotal:

The developer's response is simply to blame the antivirus programmes.
I believe that, given the level of detection, it is up to the developer to contact the publishers to understand the source of this problem.
It is difficult to exclude an executable file with such a high VirusTotal score, especially since it will likely need to be re-added with each update.

Could you please reopen this issue ?

[scidomino]

Going to investigate further...

[scidomino]

The 5.0.0 version of these executables is not flagged by anything. I'm going to see which versions of clipboardy are flagged so see which versions we exclude to avoid this.

[scidomino]

Version 5.2.0 is the newest one that comes up clean (here and here). Version 5.3.0 and 5.3.1 are both flagged.

I will change our code to require a version 5.2.x