Program Overview
GitHub runs a bug bounty program on HackerOne. The program has 27 in-scope assets.
27
In-Scope Assets
1d
Avg Response
75%
Efficiency
37d
Avg Bounty Time
49d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.github.net | URL | Critical | Bounty |
| *.githubapp.com | URL | Critical | Bounty |
| *.githubusercontent.com | URL | Critical | Bounty |
| Copilot | OTHER | Critical | Bounty |
| Copilot Chat on dotcom | OTHER | High | Bounty |
| Copilot Coding Agent | OTHER | Critical | Bounty |
| Copilot Spaces | OTHER | Critical | Bounty |
| Copilot for Business | OTHER | Critical | Bounty |
| Dependabot | OTHER | Critical | Bounty |
| GitHub CLI | DOWNLOADABLE_EXECUTABLES | High | Bounty |
| GitHub CSP | OTHER | High | Bounty |
| GitHub Desktop | DOWNLOADABLE_EXECUTABLES | Critical | Bounty |
| GitHub Enterprise Cloud | OTHER | Critical | Bounty |
| GitHub Enterprise Cloud with Data Residency (GHEC-DR) | OTHER | Critical | Bounty |
| GitHub Enterprise Server | HARDWARE | Critical | Bounty |
| GitHub Pages | OTHER | Critical | Bounty |
| GitHub Production Credentials | OTHER | Critical | Bounty |
| GitHub Spark | OTHER | Critical | Bounty |
| GitHub for mobile | OTHER | Critical | Bounty |
| api.github.com | URL | Critical | Bounty |
| classroom.github.com | URL | Critical | Bounty |
| education.github.com | URL | Critical | Bounty |
| gist.github.com | URL | Critical | Bounty |
| github.com | URL | Critical | Bounty |
| npm CLI | DOWNLOADABLE_EXECUTABLES | High | Bounty |
| npmjs.com | URL | Critical | Bounty |
| npmjs.org | URL | Critical | Bounty |
Out-of-Scope Assets
- *.github.io
- Atom
- Electron
- GitHub Classroom Assistant
- blog.github.com
- community.github.com
- enterprise.github.com
- git.io
- github.blog
- http://education.github.com/forum
- shop.github.com
- spectrum.chat
Tips for Hacking GitHub
- Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
- Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
- Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
- Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
- Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.
Frequently Asked Questions
How do I start hacking GitHub?
Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.
Does GitHub pay bounties?
Yes, GitHub offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does GitHub accept?
GitHub accepts reports for vulnerabilities found in their 27 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.