- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 7
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 2 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 2 days
| First Response | 2 days |
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this Policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
7 assets you may test.
Wildcard domains 5
- *.coinpass.com Critical No bounty
- *.oanda.com Critical No bounty
- *.oanda.jp Critical No bounty
- *.tmsbrokers.com Critical No bounty
- *.tms.pl Critical No bounty
Android apps 1
- com.oanda.fxtrade Critical No bounty
iOS apps 1
- 370922777 Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from OANDA (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
Only interact with accounts you own or with explicit permission of the account holder
-
All testing on our program must be done using an account registered with your unique @wearehackerone.com alias to be considered for validation
-
All tests on the trading platform can only be done on the DEMO (Practice) environment
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device
-
Previously known vulnerable libraries without a working Proof of Concept
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability
-
Missing best practices in SSL/TLS configuration
-
Any activity that could lead to the disruption of our service (DoS)
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or bruteforce issues on non-authentication endpoints
-
Missing best practices in Content Security Policy
-
Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers (less than 2 stable versions behind the latest released stable version)
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
-
Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 4 minutes 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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Updates
| Date | Details |
|---|---|
| 2022-09-01 | Removed *.investmentuniversity.pl from scope |
OANDA is an innovator in computer engineering and financial modeling that provides online trading and currency information services to everyone, from individuals to large corporations; portfolio managers to financial institutions. We are a market maker and a trusted source for currency data with one of the world's largest historical, high frequency, filtered currency databases.
We are looking forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Response Targets
OANDA will make a best effort to meet the following SLOs for hackers participating in our program:
| Type of Response | SLO in business days |
|---|---|
| First Response | 2 days |
| Time to Triage | 5 days |
| Time to Resolution | depends on severity and complexity |
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
- Follow HackerOne's disclosure guidelines
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced)
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report
- Social engineering (e.g. phishing, vishing, smishing) is prohibited
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder
- All researchers on HackerOne have an email alias in the format [email protected], which automatically forwards to your real email address. All testing on our program must be done using an account registered with your unique @wearehackerone.com alias to be considered for validation
- If you would like to create additional test accounts, add a plus (“+”) sign and any combination of words or numbers after your username. For example: [email protected]. This enables you to test different attack vectors / account levels without targeting other users or creating multiple HackerOne profiles
- All tests on the trading platform can only be done on the DEMO (Practice) environment
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Missing best practices in SSL/TLS configuration
- Any activity that could lead to the disruption of our service (DoS)
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or bruteforce issues on non-authentication endpoints
- Missing best practices in Content Security Policy
- Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers (less than 2 stable versions behind the latest released stable version)
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
Safe Harbor
Any activities conducted in a manner consistent with this Policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this Policy, we will take steps to make it known that your actions were conducted in compliance with this Policy.
Thank you for helping keep OANDA and our users safe!