- Top reward
- $7,000
- Top severity paid
- Critical
- Assets in scope
- 8
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $7,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 |
|
$7,000 from $501 |
| High |
|
$5,000 from $301 |
| Medium |
|
$750 from $101 |
| Low |
|
$300 from $50 |
- 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, 2 excluded.
Web 8
- cdn.arkoselabs.com Critical
- client-api.arkoselabs.com Critical
- customer-sessions.arkoselabs.com Critical
- demo.arkoselabs.com Critical
- iframe.arkoselabs.com Critical
- portal.arkoselabs.com Critical
- verify.arkoselabs.com Critical
- www.arkoselabs.com Critical
Out of scope (2)
- developer.arkoselabs.com
- https://status.arkoselabs.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Arkose Labs (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.
-
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.
-
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.
Not accepted
-
Reports from automated tools or scans
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Reports of insecure SSL/TLS ciphers
-
Any activity that could lead to the disruption of our service (DoS).
-
Rate limiting or bruteforce issues on non-authentication endpoints.
-
Vulnerabilities only affecting users of outdated or unpatched browsers
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
-
xmlrpc.php file being enabled for WP site.
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 5 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
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.
Arkose Labs protects some of the world’s largest platforms from bots, fraud and account takeover, so the security of our own products matters to our customers. We welcome research from the security community and reward valid, well-documented vulnerabilities.
Response Targets
Arkose Labs 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
- Time to bounty (from triage) - 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 Arkose Labs.
- Follow HackerOne's disclosure guidelines.
Testing Guidance
To better understand Arkose Labs Products and its core functions, please refer to the website provided - https://developer.arkoselabs.com/docs/welcome-to-arkose-labs.
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.
- 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.
Focus Areas
- Authentication bypass
- Remote code execution
- Obtaining user information
- Injection attacks
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:
- Reports from automated tools or scans
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
- Any activity that could lead to the disruption of our service (DoS).
- Rate limiting or bruteforce issues on non-authentication endpoints. As for authentication endpoints, any brute force attempts must result in Account Take-over (ATO).
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
- xmlrpc.php file being enabled for WP site.
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 Arkose Labs and our users safe!