Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ATTENTION!] Potentially malicious release file in v0.1.0-alpha.8 #306

Open
Spacelord09 opened this issue May 29, 2023 · 3 comments · Fixed by #335
Open

[ATTENTION!] Potentially malicious release file in v0.1.0-alpha.8 #306

Spacelord09 opened this issue May 29, 2023 · 3 comments · Fixed by #335

Comments

@Spacelord09
Copy link

Just fyi: Some antivirus scanners detect the binary as Gen:Variant.Lazy.324998.

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

@Nerixyz
Copy link
Owner

Nerixyz commented May 29, 2023

Thanks for opening the issue! This is a false positive. It's really hard to prove that on GitHub releases, as you don't see who uploaded a file and CI doesn't currently add a hash to verify. Here, the GitHub actions runner uploaded the file - i.e. it came straight from CI (specifically this run - build script).

My guess for why this triggered is because of the autostart prompt and the config file, or because of the global mutex to ensure only a single instance of the program exists. I'll try to investigate a bit more.

@Spacelord09
Copy link
Author

Hey, thanks for the fast Response!
Just found this: https://www.f-secure.com/v-descs/lazy.shtml

@Nerixyz
Copy link
Owner

Nerixyz commented Aug 3, 2023

That PR didn't fix this issue.

@Nerixyz Nerixyz reopened this Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants