- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $1,500
- for critical bugs, from $100.
- Report on Bugcrowd
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Bugcrowd lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$1,500 from $1,000 |
| High |
|
$600 from $300 |
| Medium |
|
$300 from $100 |
| Low |
|
$50 |
- Safe harbor
-
Full
Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original
Earlier reward tables (1)
- 11 Nov 2026 to 11 Nov 2026: Critical up to $1,500
Scope
4 assets you may test, 1 excluded.
Web 2
- https://www.osl.com/en
- https://www.osl.com/hk-en
Android apps 1
- https://play.google.com/store/apps/details?id=com.oslmobile.global
iOS apps 1
- https://apps.apple.com/es/app/osl-buy-bitcoin-crypto/id6743699672
Out of scope (1)
- https://www.osl.com/id-id
Rules
What the policy asks of you, and the bug types it won't reward, quoted from OSL Managed Public Bug Bounty Engagement (via Bugcrowd)'s policy.
While testing
-
Use of automated scanners without prior approval.
-
please include the following custom HTTP header in all of your requests: X-Bug-Bounty:<bugcrowdusername>
-
Do not submit more than one vulnerability per report.
-
If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding.
Not accepted
-
P5 vulnerabilities
-
DoS/DDoS/Network DoS
-
Rate limiting bypass attempts
-
Email bombing flooding
-
Subdomain takeover on unused subdomains
Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 56 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://www.osl.com/id-id (out of scope)
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 bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
OSL is Asia’s leading stablecoin trading and payment infrastructure. Our mission is to reshape the global financial system and make money move as freely as information. Through this program, we aim to leverage the global security community's expertise to identify vulnerabilities before malicious actors can exploit them, ensuring the safety of our users' digital assets. Ratings/Rewards For the initial prioritization/rating of findings, this engagement will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.
Targets
Testing is only authorized on the targets listed as in scope. Any domain/property of OSL Group not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to OSL Group, you can report it to this engagement. However, be aware that it is ineligible for rewards or points-based compensation. Engagement Guidelines We do not accept reports that contain low-effort or AI-generated content. Submissions must demonstrate original analysis, clear understanding of the issue, and actionable detail. Reports lacking meaningful human input will be rejected Potential post-exploitation scenarios: If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding. We will work with you to evaluate the vulnerability and award you accordingly for the final impact and severity Report Guidelines Vulnerabilities discovered on multiple paths, endpoints, parameters will be treated as duplicates. This includes findings across different environments (e.g., development, staging, production) unless the impact or exploitation method is materially different. Please submit only one report Reports must contain the role used for testing (if any), a clear explanation of the issue and the security impact along with detailed steps to reproduce it. If the issue cannot be reliably reproduced based on your report, it may be considered ineligible for a reward Do not submit more than one vulnerability per report. In cases where demonstrating impact requires chaining multiple vulnerabilities together, those can be included in the same report as long as the linkage is clearly explained Access/Traffic Identification To ensure uninterrupted access and avoid rate-limiting or blocking during your testing, please include the following custom HTTP header in all of your requests: X-Bug-Bounty: Credentials To gain access to the application, please sign up for an account using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here . You may register for accounts here . N-day/Third party 0-day Policy When N-Day bugs are released to the public, we will consider these as in scope after 14 days has gone by e.g: N-day released on 01/01/2025, we would consider it in-scope on 01/15/2025 Stolen/Breached Credentials If you happen to identify vulnerabilities involving data that has been exposed or leaked such as dark web forums or leaked credential sites, you can report it to this engagement. However, be aware that it is only eligible for points-based compensation. This policy helps maintain the highest standard of operational confidentiality, integrity, and compliance. Excluded Submission Types P5 vulnerabilities Availability/volumetric testing e.g.: DoS/DDoS/Network DoS Rate limiting bypass attempts Email bombing flooding Subdomain takeover on unused subdomains Out of Scope Use of automated scanners without prior approval. Interacting or manipulate other stakeholders and their associated accounts including: Social engineering attacks Phishing attacks Physical attacks Third party providers and services Staging and development environments Internal corporate networks Employee personal accounts or devices Potential post-exploitation scenarios : If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding. We will work with you to evaluate the vulnerability and award you accordingly for the final impact and severity. Safe Harbor When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire through the Bugcrowd Support Portal before going any further.
In scope (in scope)
Target Information: OSL is the world’s first SFC-licensed and insured digital asset platform. OSL offers custody, omnibus, tokenisation and wealth management services, which deliver institutional clients in addition to professional and retail investors access to the best-in-class digital asset platform, along with a fully regulated liquidity pool. Mobile apps: Please note that different OSL entities are registered in different geographies' app stores. The scope is strictly limited to our HK and global entities.
Out of the Scope (out of scope)
Is out of the scope even if accessed via the main website.