Skip to content

Instantly share code, notes, and snippets.

Avatar
:octocat:
hacks

x1m x1mdev

:octocat:
hacks
View GitHub Profile
View keybase.md

Keybase proof

I hereby claim:

  • I am x1mdev on github.
  • I am x1m (https://keybase.io/x1m) on keybase.
  • I have a public key ASAX8-Eejl59lUElYM9DqOTu7Mzbys5CfQ68Gm7yHiw3mgo

To claim this, I am signing this object:

@x1mdev
x1mdev / github_bugbountyhunting.md
Created Sep 28, 2017 — forked from EdOverflow/github_bugbountyhunting.md
My tips for finding security issues in GitHub projects.
View github_bugbountyhunting.md

GitHub for Bug Bounty Hunters

GitHub repositories can disclose all sorts of potentially valuable information for bug bounty hunters. The targets do not always have to be open source for there to be issues. Organization members and their open source projects can sometimes accidentally expose information that could be used against the target company. in this article I will give you a brief overview that should help you get started targeting GitHub repositories for vulnerabilities and for general recon.

Mass Cloning

You can just do your research on github.com, but I would suggest cloning all the target's repositories so that you can run your tests locally. I would highly recommend @mazen160's GitHubCloner. Just run the script and you should be good to go.

$ python githubcloner.py --org organization -o /tmp/output
View keybase.md

Keybase proof

I hereby claim:

  • I am x1mdev on github.
  • I am x1m (https://keybase.io/x1m) on keybase.
  • I have a public key ASCGT4SiLc2QQ1_PWEmEUEXur8PsF3wRW30VDC0iLjlUzAo

To claim this, I am signing this object: