- Top reward
- $3,000
- Top severity paid
- Critical
- Assets in scope
- 8
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $3,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$3,000 |
| High |
|
$1,500 |
| Medium |
|
$500 |
| Low |
|
$150 |
- Response
-
Within 5 days
Time to first response (from report submit) - 5 business days
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
8 assets you may test, 4 excluded.
Web 3
- api.prod.whoop.com Critical
- app.whoop.com Critical
- shop.whoop.com Critical
Android apps 1
- com.whoop.android Critical
iOS apps 1
- com.whoop.iphone Critical
Products and areas 3
- join.whoop.com Critical
- WHOOP 4.0 STRAP Critical
- WHOOP 5.0/MG STRAP Critical
Out of scope (4)
- Azure AD, Google Drive, Link Sharing Websites
- Credit/Debit Card Testing
- Support System
- okta.whoop.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Whoop Bug Bounty (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Do not engage in attack attempts that involve Support systems such as Support Chat, Intercom, Iterable, Salesforce, etc.
-
Do not test with accounts you do not own.
-
Do not commit destructive actions to accounts you do not own, this includes writes/edits/deletes.
-
Do not randomly fuzz into our APIs, your testing should be methodical and reproducible
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
Not accepted
-
Public keys found on web properties are generally not accepted unless you are able to demonstrate pulling non-public information
-
Bypassing web page sequencing without demonstrating a successful purchase/impact will not be accepted
-
Credentials and/or API keys of customers found on the internet (i.e: GitHub) will generally not be accepted unless they are a WHOOP employee’s credentials
-
Clickjacking on pages with no sensitive actions.
-
Unauthenticated/logout/login CSRF.
-
XSS without impact
-
Dangling DNS without impact
-
Subdomain takeover without impact
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Brute force attacks where the only valid submissions were the result of WayBack Machine research - this will be marked as spam
-
“Leaked” credentials that are only found in the WayBack machine - this will be marked as spam
-
User credentials for whoop posted publicly by the user themselves - this will be marked as N/A
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
Azure AD, Google Drive, Link Sharing Websites (out of scope)
-
Scope added
Credit/Debit Card Testing (out of scope)
-
Scope added
okta.whoop.com (out of scope)
-
Scope added
Support System (out of scope)
-
Scope added
api.prod.whoop.com
-
Scope added
app.whoop.com
-
Scope added
com.whoop.android
-
Scope added
com.whoop.iphone
-
Scope added
join.whoop.com
-
Scope added
shop.whoop.com
-
Scope added
WHOOP 4.0 STRAP
-
Scope added
WHOOP 5.0/MG STRAP
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
At WHOOP, our mission is to unlock human performance. We exist to improve the lives of our members, not invade their lives. Like all companies providing wearable devices and health monitoring services, WHOOP manages personal and sensitive data of our members. We take privacy seriously, and understand that we have a responsibility to maintain the privacy of our members’ data. As part of our “Cybersecurity as a Product” mindset we recognize that security features earn and maintain trust of our members. This Responsible Disclosure Policy demonstrates our deep commitment to maintain the privacy of our members’ data. We encourage anyone who has discovered a potential vulnerability at WHOOP to report it to us, and we are committed to working with the reporter to validate and remediate vulnerabilities.
But our responsibility does not end there. As a beneficiary of open-source software (FOSS), we also recognize that security issues we find in the code, tools and software we use should be responsibly disclosed to the appropriate code maintainers and vendors.
We do not provide credentials. You are welcome to purchase or trial WHOOP in order to obtain an account.
Program Rules
- Do not engage in attack attempts that involve Support systems such as Support Chat, Intercom, Iterable, Salesforce, etc. If you generate a ticket queue volume we may ban you from the program.
- Any reports without demonstrated impact to Confidentiality, Availability and/or Integrity will not be accepted.
- Do not test with accounts you do not own.
- Do not commit destructive actions to accounts you do not own, this includes writes/edits/deletes.
- Do not randomly fuzz into our APIs, your testing should be methodical and reproducible
- Please provide detailed reports with reproducible steps.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
Response Targets
Whoop will make a best effort to meet the following response targets for hackers participating in our program:
- Time to first response (from report submit) - 5 business days
- Time to triage (from report submit) - 10 business days
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Public keys found on web properties are generally not accepted unless you are able to demonstrate pulling non-public information
- Bypassing web page sequencing without demonstrating a successful purchase/impact will not be accepted
- Credentials and/or API keys of customers found on the internet (i.e: GitHub) will generally not be accepted unless they are a WHOOP employee’s credentials
- Clickjacking on pages with no sensitive actions.
- Unauthenticated/logout/login CSRF.
- XSS without impact
- Dangling DNS without impact
- Subdomain takeover without impact
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing best practices in SSL/TLS configuration.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Brute force attacks where the only valid submissions were the result of WayBack Machine research - this will be marked as spam
- “Leaked” credentials that are only found in the WayBack machine - this will be marked as spam
- Scans for S3 buckets and other assets (GitHub, Netlify, etc.) on the internet that have the word “whoop” but do not actually prove WHOOP ownership - this will be marked as spam
- User credentials for whoop posted publicly by the user themselves - this will be marked as N/A
- Any claim of ordering free or heavily discounted WHOOP merchandise will be marked as spam without evidence of the order actually arriving to you and a valid oderId. Illegitimate orders can sometimes be placed in our system but our logistics process will flag and cancel the order if it is not meet our expectations for a valid order.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep WHOOP and our users safe