3 ms·
LPT: put your executable binary on GitHub/GitLab/SourceForge/... These locations are whitelisted since they have a ton of fresh binaries. Malware writers use t
by jrkfkgmfmr 5y ago
LPT: put your executable binary on GitHub/GitLab/SourceForge/... These locations are whitelisted since they have a ton of fresh binaries.
Malware writers use this trick to bypass SmartScreen. Chrome's equivalent protection also whitelists GitHub/...
- stordoff 5y agoNot sure this works. Just grabbed a build of WhyNotWin11[1] released 20 hours ago, and I get "Microsoft Defender SmartScreen prevented an unrecognised app from starting. Running this app might put your PC at risk." [1] https://github.com/rcmaehl/WhyNotWin11 https://github.com/rcmaehl/WhyNotWin11 (used for test as I thought I remembered seeing this with a build from earlier this week)
- laurent123456 5y agoI don't think that works, as I had an app hosted on GitHub, a signed one actually, and it was still showing the SmartScreen warning at first. It took a few days to go away.
- ronsor 5y agoWell that's actually pretty concerning, and it only shows how broken these "security" "features" really are.
- flohofwoe 5y agoNo, this definitely doesn't work, random installers and executables downloaded from github.com definitely show the SmartScreen popup.
- jrockway 5y agoThat's my experience as well. I think that after enough people install something, Microsoft starts trusting it, so it's usually fine for a major release of a popular package. Nightly builds of less popular packages? I always get the popups. (Although oddly, not on any of my projects that I release Windows binaries for...)