Right after reading what we shared in our internal list, this information and a little bit of Github Hacking proved that GitHub is a Disneyland of information leakage. We tried a lot of different searches and some interesting or I could say, VERY INTERESTING, as you see below.
How about finding some possible 0days? Backdoors? Hell yeah! It's possible too.
Check out this GitHub "Dork":
stars:>1000 forks:>100 extension:php "eval(preg_replace("
We searched for big projects who have more than 1000 stars, 100 forks, files with PHP extension and a possible flaw that allows Remote Code Execution.
Check out other prefixes that might help you keeping your search improved GitHub Search Cheat Sheet.
Lots of FUN isn't ? We could probably find just about anything, the sky is the limit!
So to make our lives easier we developed a tool to grab those information in a more automated way:
You can check the code and download it from here (but keep in mind that it is still in beta version).
Take care about what information you share. Lots of sensitive information could probably be over there. Search for information about your company before the bad guys do.