We understand the devastating impact poor security can have on the whole industry and value the efforts of security researchers to keep our community safe.
We encourage responsible disclosure of security vulnerabilities via our bug bounty program described on this page.
The scope of our bounty program covers:
- Digital asset balances
- Customers information
A report must be valid, in scope report in order to qualify for a bounty. A valid report is any in-scope report that clearly demonstrates a software vulnerability that harms Multi or Multi customers. Multi will determine in its sole discretion whether a report is eligible for a reward and the amount of the award.
Multi pledges not to initiate legal action for security research conducted pursuant to all Bug Bounty Program policies, including good faith, accidental violations. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act, the DMCA, and applicable anti-hacking laws such as Cal. Penal Code 502(c). We will not bring a DMCA claim against researchers for circumventing the technological measures we have used to protect the applications in the scope of the Bug Bounty Program.
If legal action is initiated by a third party against you and you have complied with the Bug Bounty Program policy, we will take steps to make it known that your actions were conducted in compliance with this policy. Please understand that if your security research involves the networks, systems, information, applications, products, or services of another party (which is not us), that third party is not bound by our pledge and may determine whether to pursue legal action. Multi cannot and does not authorize security research on other entities.
Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy. This report should include a brief description of your intended conduct so that we may determine whether it is consistent with the Bug Bounty Program policy.
We believe it is critical to provide these assurances in order to allow security researchers to fully investigate potential security vulnerabilities. As such, we embrace the standardization of policy language that provides legal protection to security researchers as a part of the #legalbugbounty project.
Complying with the Bug Bounty Program policy requires researchers to adhere to “Responsible Disclosure”. Responsible Disclosure includes:
- Providing Multi a reasonable amount of time to fix a vulnerability prior to sharing details of the vulnerability with any other party.
- Making a good faith effort to preserve the confidentiality and integrity of any Multi customer data.
- Not defrauding Multi customers or Multi itself in the process of participating in the Bug Bounty Program.
- Not profiting from or allowing any other party to profit from a vulnerability outside of Bug Bounty Program payouts from Multi.
- Reporting vulnerabilities with no conditions, demands, or ransom threats.
Multi considers Social Engineering attacks against Multi employees be a violation of Program Policies. Researchers engaging in Social Engineering attacks against Multi employees will be banned from the Multi Bug Bounty program. We define Social Engineering as acts that influence people to perform security-impacting actions or divulge confidential information.
In order to be deemed valid, a report must demonstrate a software vulnerability in a service provided by Multi that harms Multi or Multi customers. Reports that include a clear Proof of Concept or specific step by step instructions to replicate the vulnerability are considerably more effective at communicating a researcher’s findings and are therefore far more likely to be deemed valid.
A report must be valid, in scope report in order to qualify for a bounty. Multi awards bounties based on the severity of the vulnerability. We determine severity based on two factors: Impact and Exploitability.
Impact describes the effects of successful exploitation upon Multi systems or customers. We make this assessment primarily by examining the effects of exploitation on confidentiality, integrity, or availability of underlying information. Vulnerabilities that require considerable response and remediation efforts or could result in reputational damage are also considered to have a greater impact. For example:
- Critical Impact: Attackers can read or modify Sensitive Data in a system, execute arbitrary code on the system, or exfiltrate digital assets in some way.
- Low Impact: Attackers can gain small amounts of unauthorized, low sensitivity information impacting a subset of users, or slightly impact the accuracy and performance of a system. (Please note that Denial of Service bugs will be considered on a case-by-case basis. Lack of rate limiting in Multi products has been accepted as valid reports in the past but will be not considered valid unless a clear bypass of the limit is demonstrated. Denial of Service issues that don't impact the availability of funds or user data will not likely be accepted as a valid report.)
Exploitability describes the difficulty of actively exploiting the vulnerability itself. We make this assessment primarily based on the prerequisites for exploitation, including the level of access required, availability of information critical for successful exploitation, and the likelihood of alignment of required factors outside the attacker's direct control such as social engineering requirements or timing requirements. For example:
- Critical Exploitability: Attackers can unilaterally exploit the finding without significant roadblocks or special conditions outside attacker control.
- Low Exploitability: Exploitation is difficult due to several requirements, such as access limitations, complicated social engineering, guessing unknown values, or alignment of unpredictable race conditions.
Severity is determined as a combination of Impact and Exploitability. For example:
- Critical Severity: a state of immediate, easily accessible threat of large-scale compromise or irreversible damage to Multi or Multi customers.
- Low Severity: a state of no immediate threat where an opportunity exists for an improvement that may mitigate a potential future vulnerability.
In order to provide general guidelines to researchers regarding the payouts that can be expected for a given report, Multi uses the severity of a report to place the report into one of the following tiers.
|Critical||$1,000 - $5,000|
|Severe||$500 - $1,000|
|Moderate||$200 - $500|
|Low||Up to $200|
Bonuses in excess of the tier ranges can be awarded based on the severity of the vulnerability or creativity of the exploitation. Researchers are also more likely to earn a larger reward for exceptionally clear and high-quality reports.
Previous bounty amounts are not considered a precedent for future bounty amounts. Software is constantly changing and therefore the given security impact of the exact same vulnerability at different times in the development timeline can have drastically different security impacts.
The Multi Bug Bounty program scope covers all software vulnerabilities in services provided by Multi.
Specific domains hosting Multi services are provided below:
- *.multi.io (All assets on multi.io and subdomains, excepting services provided by third parties)
Please view the scope section for a more detailed list of in-scope and out-of-scope assets. Companies Multi has acquired are not in the scope of the bug bounty program unless they are specifically added to the scope section and declared in scope.
Additionally, all vulnerabilities that require or are related to the following are out of scope:
- Social engineering
- Physical security
- Non-security-impacting UX issues
- Deprecated Open Source libraries are not in scope. If you would like to report a vulnerability for one of these libraries, please submit it on GitHub via an issue or PR. Note: we do accept vulnerability reports through HackerOne for our currently supported, actively maintained open-source libraries.
- Vulnerabilities or weaknesses in third-party applications that integrate with Multi
If you feel that a particular asset or activity not mentioned here should be in scope, please submit a report along with a brief description of why you believe that the asset should be covered by this scope.
Bugs to be reported via request form and selecting category "Bug Bounty Program" here: https://support.multi.io/hc/en-us/requests/new
We reserve the right to modify the Bug Bounty Program or cancel the Bug Bounty Program at any time.
The current Bug Bounty Program as described on this page is v1.1 of our Bug Bounty Program.