- Top reward
- $10,000
- Top severity paid
- Critical
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $10,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$10,000 from $6,000 |
| High |
|
$5,000 from $2,000 |
| Medium |
|
$1,500 from $750 |
| Low |
|
$500 from $100 |
Scope
6 assets you may test.
Wildcard domains 4
- *.projectbaseline.com Low
- *.signalpath.com Critical
- *.verily.com Critical
- *.verilyme.com Critical
Android apps 1
- https://play.google.com/store/apps/details?id=com.verily.me Critical
iOS apps 1
- https://apps.apple.com/us/app/verily-me/id6448808133 Critical
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Verily Life Sciences (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
-
Ask the program team before submitting vulnerabilities on assets that have not been explicitly listed in the program scope.
-
Social engineering (e.g., phishing, vishing, smishing) is prohibited.
-
Attacks that affect the availability of Verily's services such as denial-of-service attacks are prohibited.
-
Using tools that perform DNS brute forcing of any kind 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.
-
Please use your **hacker email alias** (e.g. [email protected]) when testing.
Not accepted
-
URL redirections
-
vulnerabilities requiring unlikely or impractical user interaction steps
-
"logout" cross-site request forgery
-
banner or version information leaks
-
user enumeration
Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 18 minutes 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
https://*.projectbaseline.com/
-
Scope added
https://*.signalpath.com/
-
Scope added
https://*.verily.com/
-
Scope added
https://*.verilyme.com/
-
Scope added
https://apps.apple.com/us/app/verily-me/id6448808133
-
Scope added
https://play.google.com/store/apps/details?id=com.verily.me
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.
Disclosure Policy
- Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- Ask the program team before submitting vulnerabilities on assets that have not been explicitly listed in the program scope. Submissions will be accepted and reviewed by the team only if the asset is confirmed to be Verily-owned.
- Social engineering (e.g., phishing, vishing, smishing) is prohibited.
- Attacks that affect the availability of Verily's services such as denial-of-service attacks are prohibited. Please avoid using scanners or vulnerability testing tools that generate high volumes of traffic to avoid being flagged by our monitoring systems.
- Using tools that perform DNS brute forcing of any kind is prohibited.
- Leveraging black hat SEO techniques, spamming people, breaking and entering into Verily offices are also prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
- Vulnerability disclosures that do not qualify for rewards through this program include URL redirections, vulnerabilities requiring unlikely or impractical user interaction steps, "logout" cross-site request forgery, banner or version information leaks, and user enumeration.
- Only interact with accounts you own or with the explicit permission of the account holder.
- The following subdomains are excluded from this program's scope - "enroll.onduo.com" and "helix.verily.com".
Test Plan
- Users are able to sign up for free accounts through some of our in-scope domains and mobile apps. We do not provide credentials for testing at this time.
- Please use your hacker email alias (e.g. [email protected]) when testing.
Session Layer: HTTP Headers
Researchers should add headers to requests such as:
- “X-HackerOne-Research: [H1 username]"
Thank you for helping keep Verily and our users safe!