search

goliate / hidden-tear

ransomware open-sources
729 stars 389 forks source link

Why do you have the Binary (EXE) file in your repo - Chrome flags as / malicious dangerous #9

Open joe-oli opened 3 years ago

joe-oli commented 3 years ago

Why do you have the Binary (EXE) file in your repo? are you trying to infect somebody ? Chrome blocked it as dangerous . Avira blocked as dangerous.

Having source is different, but the binary may be dangerous, even if you say it is not.

goliate commented 3 years ago

Ceci n'est juste qu'une copie d'un dépôt de l'auteur.

J'ai cloner son projet pour l'avoir sous la main pour moi travaillé

hackthedev commented 3 years ago

@joe-oli I do have a ransomware project too and it does contain the .exe file too because github simply uploads it too. Sure you could use the .gitignore file, but if you make your inital commit you might have not set it up from the beginning, and since chrome and or your local anti-virus will remove it anyways its not a big deal.

Also by downloading a project like this you should know what you're doing in the first place. If you download this repo and build it a new exe file is created anyways so... like i said: Know what you're doing.

marcus-cr commented 3 years ago

This issue should be closed.

If you are concerned that the exe was uploaded along the source code then you should not be browsing this project (unless you know what you're doing).