- Top reward
- $3,000
- Top severity paid
- Critical
- Assets in scope
- 5
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $3,000
- for critical bugs.
- Report on HackenProof
- Submit through the program page.
- Replies within 3 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackenProof lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$3,000 |
- Response
-
Within 3 days
First Response 3d
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
5 assets you may test, 4 excluded.
Android apps 1
- https://play.google.com/store/apps/details?id=com.exmo
APIs 1
- https://api.exmo.com
Domains 1
- exmo.com
iOS apps 1
- https://apps.apple.com/app/id1505496232?mt=8
Wildcard domains 1
- *.exmo.com
Out of scope (4)
- exmo-coin.exmo.com
- info.exmo.com
- support.exmo.com
- https://exmo.com/blog/*
Rules
What the policy asks of you, and the bug types it won't reward, quoted from EXMO (via HackenProof)'s policy. "We" in these lines means the program, not this site.
While testing
-
Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
-
Make every effort not to damage or restrict the availability of products, services, or infrastructure
-
Avoid compromising any personal data, interruption, or degradation of any service
-
Don’t access or modify other user data, localize all tests to your accounts
-
Perform testing only within the scope
-
Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
-
Don’t spam forms or account creation flows using automated scanners
-
In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
-
Don’t break any law and stay in the defined scope
-
Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
Not accepted
-
Vulnerabilities in third-party applications
-
Best practices concerns
-
Social engineering, phishing, physical, or other fraud activities
-
Publicly accessible login panels without proof of exploitation
-
Reports that generated by scanners or any automated or active exploit tools
-
Most brute-forcing issues without clear impact
-
Denial of service (DoS/DDoS)
-
Theoretical issues
-
Moderately Sensitive Information Disclosure
-
Spam (sms, email, etc)
-
Missing HTTP security headers
-
User account enumeration
-
Self-XSS that cannot be used to exploit other users
-
Login & Logout CSRF
-
Weak Captcha
-
Lack of Secure and HTTPOnly cookie flags
-
OPTIONS/TRACE HTTP method enabled
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Reflected File Download (RFD)
-
Mixed HTTP Content
-
MitM and local attacks
-
Disclosure of non sensitive information, such as product version
-
Attacks requiring physical access to a user's device
-
Vulnerabilities that require root/jailbreak
-
Vulnerabilities requiring extensive user interaction
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour 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 hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Bug bounty EXMO: Program info EXMO Company: EXMO Scope Review: 250071 Submissions: 177 Total rewards: $9,630 Reputation 50 points required PoC Required Program left: 84 days ago Finished Submit report Contest is not active Program info Hackers 118 Reports 0 EXMO is a global cryptocurrency exchange. The platform was established in 2014 and is constantly expanding its functionality, adding new assets to the listing, and, most importantly, increasing the number of customers. All Scope Focus Area Program Rules Scope Search targets In scope Target │ Type │ Severity exmo.com Copy Web │ Critical .exmo.com Copy Web │ Critical https://api.exmo.com Copy API │ Critical https://play.google.com/store/apps/details?id=com.exmo Copy Android │ Critical https://apps.apple.com/app/id1505496232?mt=8 Copy iOS │ Critical Out of scope Out of scope Target │ Type │ Severity info.exmo.com Copy Our blog. As well as https://exmo.com/blog/ │ Web │ None exmo-coin.exmo.com Copy Web │ None support.exmo.com Copy Web │ None Focus Area IN-SCOPE WEB VULNERABILITIES We are interested in the following vulnerabilities: Business logic issues Payments manipulation Remote code execution (RCE) Injection vulnerabilities (SQL, XXE) File inclusions (Local & Remote) Access Control Issues (IDOR, Privilege Escalation, etc) Leakage of sensitive information Server-Side Request Forgery (SSRF) Cross-Site Request Forgery (CSRF) Cross-Site Scripting (XSS) Directory traversal Other vulnerability with a clear potential loss OUT-OF-SCOPE WEB VULNERABILITIES Vulnerabilities found in out of scope resources are unlikely to be rewarded unless they present a serious business risk (at our sole discretion). In general, the following vulnerabilities do not correspond to the severity threshold: Vulnerabilities in third-party applications Leaked or publicly available user credentials originating from third-party breaches or external sources not caused by vulnerabilities in our systems Any type of vulnerability that is only exploitable by stealing information, cookies, or tokens directly from a user’s device Assets that do not belong to the company Best practices concerns Recently (less than 30 days) disclosed 0day vulnerabilities Vulnerabilities affecting users of outdated browsers or platforms Social engineering, phishing, physical, or other fraud activities Publicly accessible login panels without proof of exploitation Reports that state that software is out of date/vulnerable without a proof of concept Reports that generated by scanners or any automated or active exploit tools Vulnerabilities involving active content such as web browser add-ons Most brute-forcing issues without clear impact Denial of service (DoS/DDoS) Theoretical issues Moderately Sensitive Information Disclosure Spam (sms, email, etc) Missing HTTP security headers Infrastructure vulnerabilities, including: Certificates/TLS/SSL-related issues; DNS issues (i.e. MX records, SPF records, DMARC records etc.); Server configuration issues (i.e., open ports, TLS, etc.) User account enumeration Self-XSS that cannot be used to exploit other users Login & Logout CSRF Weak Captcha Lack of Secure and HTTPOnly cookie flags Username/email enumeration via Register Page error messages CSRF in forms that are available to anonymous users (e.g. the contact form) OPTIONS/TRACE HTTP method enabled Host header issues without proof-of-concept demonstrating the vulnerability Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS Content Spoofing without embedded links/HTML Reflected File Download (RFD) Mixed HTTP Content HTTPS Mixed Content Scripts MitM and local attacks Disclosure of non sensitive information, such as product version Disclosure of public user information, such as nick name OUT OF SCOPE - MOBILE Attacks requiring physical access to a user's device Vulnerabilities that require root/jailbreak Vulnerabilities requiring extensive user interaction Exposure of non-sensitive data on the device Reports from static analysis of the binary without PoC that impacts business logic Lack of obfuscation/binary protection/root(jailbreak) detection Bypass certificate pinning on rooted devices Lack of Exploit mitigations i.e., PIE, ARC, or Stack Canaries Sensitive data in URLs/request bodies when protected by TLS Path disclosure in the binary OAuth & app secret hard-coded/recoverable in IPA, APK Sensitive information retained as plaintext in the device’s memory Crashes due to malformed URL Schemes or Intents sent to exported Activity/Service/Broadcast Receiver (exploiting these for sensitive data leakage is commonly in scope) Any kind of sensitive data stored in-app private directory Runtime hacking exploits using tools like but not limited to Frida/ Appmon (exploits only possible in a jailbroken environment) Shared links leaked through the system clipboard Any URIs leaked because a malicious app has permission to view URIs opened. Exposure of API keys with no security impact (Google Maps API keys etc.) Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic Make every effort not to damage or restrict the availability of products, services, or infrastructure Avoid compromising any personal data, interruption, or degradation of any service Don’t access or modify other user data, localize all tests to your accounts Perform testing only within the scope Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam Don’t spam forms or account creation flows using automated scanners In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity. Don’t break any law and stay in the defined scope Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission Live since 05 Nov 2021 Published date 05 Nov 2021 Last updated 23 Sep 2026 Range of bounty $50 - $3,000 Severity Critical $0 High $0 Medium $0 - $0 Low $0 CEX Web apps @Adv-adv Verified 1 @ParthaBishwas Verified 2 @johnb 3 @haxim Verified 4 @malekmohamed0 Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 60d