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

youtube-dlc.exe Trojan? #114

Closed
C0ldF opened this issue Sep 15, 2020 · 4 comments
Closed

youtube-dlc.exe Trojan? #114

C0ldF opened this issue Sep 15, 2020 · 4 comments
Labels
question Further information is requested

Comments

@C0ldF
Copy link

C0ldF commented Sep 15, 2020

Checklist

  • [ x] I'm asking a question
  • [x ] I've looked through the README and FAQ for similar questions
  • [x ] I've searched the bugtracker for similar questions including closed ones

Question

Hi, why windows defender says the youtube-dlc.exe its trojan? https://prnt.sc/uhoder

@C0ldF C0ldF added the question Further information is requested label Sep 15, 2020
@TheFrenchGhosty
Copy link

TheFrenchGhosty commented Sep 15, 2020

Because it's an unsigned exe that share some characteristics with real malware.

And because antivirus are dumb and useless.

If you are scared, build it yourself.

@blackjack4494
Copy link
Owner

Nothing I can do for now.
You can indeed build it yourself if you don't trust me. Hopefully soon everything will be build automatic (including exe).

If you have python installed I suggest you using pip install then.

Will close this for now. But feel free to keep discussing here.

@jbruchon
Copy link

jbruchon commented Sep 24, 2020

It is common for antiviruses and for Windows SmartScreen to raise concerns about binaries from open source projects. Avast Antivirus, for example, will flip out because "this file hasn't been seen by many systems yet" and will block execution until a comprehensive heuristic scan is run on the executable. Considering that a smaller project's executables will have a lot less users, this should be expected. The solution is to tell the AV to leave the file alone. If you have concerns, submit it to VirusTotal and see what that aggregate set of detections looks like.

@blackjack4494
Copy link
Owner

Some AV will trigger because they haven't seen a program before. Some will trigger even if you have like one line code in common with some known malware. The only solution would be to get an expensive certificate to sign your own program (there is no free way like let's encrypt does for websites).
I did the best I can by let the CI build on the public code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants