Program Overview
Twilio runs a bug bounty program on HackerOne. The program has 24 in-scope assets and is managed by HackerOne's triage team.
24
In-Scope Assets
6h
Avg Response
85%
Efficiency
1d
Avg Bounty Time
206d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.sip.*.twilio.com | WILDCARD | Critical | Bounty |
| Any host/web property verified to be owned by Twilio et al. | OTHER | Critical | Bounty |
| Twilio APIs | API | Critical | Bounty |
| api.segment.io | API | Critical | Bounty |
| api.sendgrid.com | URL | Critical | Bounty |
| api.twilio.com | API | Critical | Bounty |
| app.segment.com | URL | Critical | Bounty |
| app.sendgrid.com | URL | Critical | Bounty |
| http://help.twilio.com | URL | Critical | Bounty |
| http://tsock.us1.twilio.com | URL | Critical | Bounty |
| http://twilio.com/blog | URL | Critical | Bounty |
| https://segment.com/docs/connections/sources/ | URL | Critical | Bounty |
| https://www.authy.com/download/ | APPLE_STORE_APP_ID | Critical | Bounty |
| https://www.authy.com/download/ | GOOGLE_PLAY_APP_ID | Critical | Bounty |
| https://www.twilio.com/docs/authy/api | API | Critical | Bounty |
| https://www.twilio.com/docs/libraries | OTHER | Critical | Bounty |
| https://www.twilio.com/docs/verify/api | API | Critical | Bounty |
| https://www.twilio.com/en-us/blog/get-started-webrtc | OTHER | Critical | Bounty |
| https://www.twilio.com/login?g=%2fconsole%3f&t=2b1c98334b25c1a785ef15b6556396290e3c704a9b57fc40687cbccd79c46a8c | URL | Critical | Bounty |
| mc.sendgrid.com | URL | Critical | Bounty |
| sendgrid.com | URL | Critical | Bounty |
| signup.sendgrid.com | URL | Critical | Bounty |
| smtp.sendgrid.net | OTHER | Critical | Bounty |
| static*.twilio.com | WILDCARD | Critical | Bounty |
Out-of-Scope Assets
- All Kurento domains
- All Twilio acquisitions until explicitly noted under the in-scope targets
- Electric Imp and its assets
- Third-party services
- Twilio Quest
- Twilio Wireless
- TwimlBins
- Ytica and its assets
- community.segment.com
- http://apjevents.twilio.com
- http://events.cdpweek.com
- http://segment.com/contact
- http://segment.com/jobs
- http://twilio.com/en-us/company/jobs
- http://twilio.com/labs
- jobs.twilio.com
- lab.authy.com
- signal.twilio.com
- status.segment.com
- status.sendgrid.com
Tips for Hacking Twilio
- 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 Twilio?
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 Twilio pay bounties?
Yes, Twilio offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does Twilio accept?
Twilio accepts reports for vulnerabilities found in their 24 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.