Starbucks Bug Bounty Program

Program Overview

Starbucks runs a bug bounty program on HackerOne. The program has 10 in-scope assets and is managed by HackerOne's triage team.

In-Scope Assets

Asset	Type	Max Severity	Eligible
Other assets	OTHER	Critical	No Bounty
Subdomain Takeover (SDTO)	OTHER	Critical	Bounty
app.starbucks.com	URL	Critical	Bounty
com.starbucks.mobilecard	GOOGLE_PLAY_APP_ID	Critical	Bounty
com.starbucks.mystarbucks	APPLE_STORE_APP_ID	Critical	Bounty
openapi.starbucks.com	URL	Critical	Bounty
secureui.starbucks.com	URL	Critical	Bounty
www.starbucks.ca	URL	Critical	Bounty
www.starbucks.com	URL	Critical	Bounty
www.starbucksreserve.com	URL	Critical	Bounty

Out-of-Scope Assets

• Teavana
• apply.starbucks.com
• athome.starbucks.com
• careers.starbucks.com
• lsstar.starbucks.com

Tips for Hacking Starbucks

1. Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
2. Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
3. Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
4. Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
5. 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 Starbucks?

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 Starbucks pay bounties?

Yes, Starbucks offers monetary rewards for valid security vulnerabilities.

What types of vulnerabilities does Starbucks accept?

Starbucks accepts reports for vulnerabilities found in their 10 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.