Program Overview
TomTom runs a vulnerability disclosure program on HackerOne. The program has 4 in-scope assets and is managed by HackerOne's triage team.
4
In-Scope Assets
5h
Avg Response
89%
Efficiency
261d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.tomtom-global.com | WILDCARD | Critical | No Bounty |
| *.tomtom.com | WILDCARD | Critical | No Bounty |
| *.tomtomgroup.com | WILDCARD | Critical | No Bounty |
| https://github.com/tomtom-international/* | SOURCE_CODE | Critical | No Bounty |
Tips for Hacking TomTom
- 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 TomTom?
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 TomTom pay bounties?
No, TomTom runs a Vulnerability Disclosure Program (VDP) without monetary rewards. You may receive recognition or swag.
What types of vulnerabilities does TomTom accept?
TomTom accepts reports for vulnerabilities found in their 4 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.