Program Overview
inDrive runs a bug bounty program on HackerOne. The program has 118 in-scope assets.
118
In-Scope Assets
20h
Avg Response
100%
Efficiency
5d
Avg Bounty Time
64d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.indrive.com | WILDCARD | High | Bounty |
| *.indriver.com | WILDCARD | Medium | Bounty |
| *.indriverapp.com | WILDCARD | Critical | Bounty |
| ab-api-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| ab-platform-api.eu-east-1.indriverapp.com | URL | Critical | Bounty |
| alternativa.film | URL | High | Bounty |
| api-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| api.ryadom.kz | URL | Critical | Bounty |
| as-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| as-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| ath-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| ath-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| auroratechaward.com | URL | High | Bounty |
| baf-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| bdu-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| bid.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| blog.indrive.com | URL | Critical | Bounty |
| careers.indrive.com | URL | Critical | Bounty |
| cargo.indrive.com | URL | Critical | Bounty |
| cas-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| cht-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| cht-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| co-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| co-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| co-in-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| coaching.supernovas.indrive.com | URL | Critical | Bounty |
| courier-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| couriers.indrive.com | URL | Critical | Bounty |
| debug.clairvoyance.indrive.tech | URL | Critical | Bounty |
| delivery-webview.indrive.com | URL | Critical | Bounty |
| dh-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| dr-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| es-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| es-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| external.indrive.dev | URL | Critical | Bounty |
| fch-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| fe-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| fe-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| file-storage-front.eu-east-1.indriverapp.com | URL | Critical | Bounty |
| g2-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| g2-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| gt-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| gt-gw-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| gvt-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| https://*.indriver.io | WILDCARD | Critical | Bounty |
| https://cas-cf.euce1.indriverapp.com/api/passkey | URL | Critical | Bounty |
| ic3.*.indriverapp.com | WILDCARD | Critical | Bounty |
| icl-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| idp-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
| in-cf.*.aws.indriverapp.com | WILDCARD | Critical | Bounty |
Showing 50 of 118 in-scope assets. View all on HackerOne.
Out-of-Scope Assets
- bus.*.indrive.com
- servicos.indrive.com
- sinet.startup.inDriver
- super-services.indriverapp.com
Tips for Hacking inDrive
- 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 inDrive?
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 inDrive pay bounties?
Yes, inDrive offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does inDrive accept?
inDrive accepts reports for vulnerabilities found in their 118 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.