MoreLogin Bug Bounty Program
MoreLogin is a cutting-edge technology business with a focus on browser security.
Project Overview
MoreLogin is a cutting-edge technology business with a focus on browser security.
Rewards
Rewards will be provided according to the rules of this bug bounty program as outlined above. At the discretion of MoreLogin, quality, creativity, or novelty of submissions may modify payouts within a given range.
In case of multiple reports about the same issue, MoreLogin will reward the earliest submission, regardless of how the issue was reported.
CVSS standards will be used for vulnerability rating (https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator).
Websites and Applications
| Severity | Description | Reward |
|---|
| Critical | Critical severity vulnerabilities will have a significant impact on the security of the project, and it is strongly recommended to fix the critical vulnerabilities. | 1,000 ~ 1,500 USDT |
| High | High severity vulnerabilities will affect the normal operation of the project. It is strongly recommended to fix high-risk vulnerabilities. | 150 ~ 1,000 USDT |
| Medium | Medium severity vulnerability will affect the operation of the project. It is recommended to fix medium-risk vulnerabilities. | 50 ~ 150 USDT |
| Low | Low severity vulnerabilities may affect the operation of the project in certain scenarios. It is suggested that the project team should evaluate and consider whether these vulnerabilities need to be fixed. | 0 ~ 50 USDT |
Scopes
In Scope
Out of Scope
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection (e.g. url parameters, path, etc.)
- This does not exclude reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (e.g. logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as "httponly") without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys (e.g. etherscan, Infura, Alchemy, etc.)
- Any vulnerability exploit that requires browser bugs for exploitation (e.g. CSP bypass)
Prohibited Activities
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- Any testing with pricing oracles or third party smart contracts
- Attempting phishing or other social engineering attacks against employees and/or customers
- Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
Reporting Rules
- Rewards or recognition require that the MoreLogin security team can reproduce and verify an issue and that the security impact is clear
- Reproduction steps need to be clear, and may include screenshots, videos, scripts, etc
- Do not conduct social engineering and phishing to people
- Do not leak the details of the vulnerability
- Do not use a scanner for large-scale scanning. If the business system or network becomes unavailable, it will be handled according to relevant laws
- Those who test the vulnerability should try to avoid modifying the page directly, continuing popping up the message box (log is recommended for XSS verification), stealing Cookies, and obtaining aggressive payload such as user information (for blind XSS testing, please use DNSLog). If you accidentally used a more aggressive payload, please delete it in time
- Vulnerability testing is only limited to PoC (proof of concept), and destructive testing is strictly prohibited. If harms are caused inadvertently during the testing, it should be reported in time. Meanwhile, sensitive operations performed in the test, such as deletion, modification, and other operations, are required to be explained in the report
