Tools and Features that can be Used to Detect Sensitive Data Leaks from Github — Part 2

In part 1 of this blog series, we discussed a few popular osint tools that help developer’s find leaked information from their GitHub projects: GitGrabber, GitLeaks, Gitminer, Gitrob. In this part, we will continue with another few tools and some examples for each.


In the example below, some repo that belong to x-company have been dug but no leakage has been detected. For instance, when the repository of GitGraber is given, we can see that files like that contain keywordlist are detected.


If it is needed, we can ask to dig anything that you find suspicious.

This is a collection of dorks to search for sensitive data on GitHub repos. Scanning can be done by giving a user repo, company name or direct link. In the dorks list there are file name examples and Google Dorks searches through that list. Scanning doesn’t last for too long. For example, for a small company, scanning may last for about 2 minutes. It doesn’t seem to be very successful, and compared to GittyLeaks it actually is unsuccessful. But it’s still worth trying.

Github Dorks

Repo Scanner

Repo Scanner is a tool to dig passwords, private keys and similar sensitive information in Github. The process flows as follows:the wanted repo is firstly downloaded to local, then the commands are executed by going into the downloaded folder. An example done for n11 is given in the picture.

Digging process can be done for all files in a folder.

Originally published at on May 7, 2020.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store