About
Okto
Empower yourself with DeFi
Secure DeFi App with simplified Earn opportunities. Swap thousands of tokens across multiple chains. Own your crypto with self-custody!
Program Rules
Testing Policy and Responsible Disclosure
Please adhere to the following rules while performing research on this program:
- Denial of service (DoS) attacks on Okto applications, servers, networks or infrastructure are strictly forbidden.
- Avoid tests that could cause degradation or interruption of our services.
- Do not use automated scanners or tools that generate large amount of network traffic.
- Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
- Do not copy any files from our applications/servers and disclose them.
- No vulnerability disclosure, full, partial or otherwise, is allowed.
Reports of leaks and exposed credentials
In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and identified outside of our program’s scope, such as:
- Exposed credentials in/from an out-of-scope asset/source
- Sensitive information exposed in/from an out-of-scope asset/source
Also, in order not to encourage dark and grey economies, in particular the purchase, resale and trade of identifiers or stolen information, as well as all types of dangerous behavior (e.g. social engineering, ...), we will not accept or reward any report based on information whose source is not the result of failure on the part of our organization or one of our employees/service providers.
This excludes, but is not limited to:
- Stolen credentials gathered from unidentified sources (e.g. …)
- Exposed credentials that are not applicable on the program’s scope
- Exposed GitHub/GitLab (or similar) instance with no direct relation with our program’s scope
- Exposed secrets (e.g. API tokens/keys or other technical credentials) that are not directly related to the program’s scope
- Exposed PII on an out-of-scope asset
To summarize our policy, you may refer to this table :
|
Source of leak is in-scope |
Source of leak belongs to Okto but is out-of-scope |
Source of leak does not belong to Okto and is out-of-scope |
Impact is in-scope (e.g. valid credentials on an in-scope asset) |
Eligible |
Eligible |
Not Eligible |
Impact is out-of-scope (e.g. valid credentials for an out-of-scope asset) |
Eligible |
Not Eligible |
Not Eligible |
Important precautions and limitations
As a complement to the Program’s rules and testing policy :
- DO NOT alter compromised accounts by creating, deleting, removing or modifying any data
- DO NOT use compromised accounts to search for post-auth vulnerabilities (they won’t be eligible anyway)
- DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.
- In case of exposed credentials or secrets, limit yourself to verifying the credentials validity
- In case of sensitive information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.
Reward Eligibility
We are happy to thank everyone who submits valid reports which help us improve the security of Okto, however only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability (see below).
- The report must contain the following elements:
- Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and Okto, and remediation advice on fixing the vulnerability
- Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
- Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
- You must not break any of the testing policy rules listed above
- You must not be a former or current employee of Okto or one of its contractors.
Reward amounts are based on:
- Reward grid of the report's scope
- CVSS scoring and actual business impact of the vulnerability upon performing risk analysis
Complements about our scopes
Okto App
Important things to know about the app :
We are mainly interested in the below:
- Web3 related Security Issues
- Accessing other user’s accounts or financial information
- Accessing the wallets of other users
- Authentication & Authorization
- Withdrawing funds
- SSL Pinning Bypass, Root detection and other security features
In Scope
Scope Type |
Scope Name |
android_application |
https://play.google.com/store/apps/details?id=com.coindcx.okto |
api |
*.okto.tech |
ios_application |
https://apps.apple.com/in/app/okto-wallet/id6450688229 |
Out of Scope
Scope Type |
Scope Name |
undefined |
All domains or subdomains not listed in the above list of 'Scopes' |
undefined |
All other third parties |
web_application |
CMS websites own by Okto (Anything related to Wordpress etc) |
web_application |
Customer support form (https://help-okto.sprinklr.com/help/) |
Firebounty have crawled on 2024-03-04 the program Okto - Bug Bounty Program on the platform Yeswehack.