Details

Response Targets

CoinSpot will make a best effort to meet the following response targets for hackers participating in our program:

Time to first response (from report submit) - 5 days
Time to triage (from report submit) - 10 days
Time to bounty (from triage) - 14 days

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 consent from the CoinSpot Team.
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 will not be eligible for a reward.
Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
Social engineering (e.g. phishing, vishing, smishing) and Attacks against our customer accounts are 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 the explicit permission of the account holder.
All Hackers must follow the rules outlined in the HackerOne Code of Conduct

Test Plan

You may register for up to two free accounts on https://www.coinspot.com.au
Please note that one test account should be registered with your Hacker Email Alias in order to be granted full access for testing - [username]@wearehackerone.com
API Documentation: https://www.coinspot.com.au/v2/api

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 and/or ineligible for bounties:

Closure of accounts with no transaction history
Enablement of 2FA without email confirmation
Reports of publicly leaked account credentials
Attacks requiring MITM or physical access to a user's device.
Rate limiting or bruteforce issues on non-authentication endpoints
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Upload of malicious files via s3 pre-signed URLs where impact cannot be demonstrated.
Known vulnerable versions of libraries or components without a working Proof of Concept.
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

Safe Harbor

CoinSpot has adopted HackerOne Gold Standard Safe Harbour!

Severity Assessment Guidelines:

The following section provides a guide on how CoinSpot determines the criticality of reported issues.

Severity	Assessment Guidelines
`Critical`	Issues with a Critical severity rating are practically exploitable by an attacker with the impact of significant loss of funds or significant impacts to the confidentiality and integrity of CoinSpot customer data. For example: Remote command execution on a CoinSpot managed system, Access to funds (digital or fiat) outside of the context of a given user, Mass unauthorised access/modification of sensitive data
`High`	Examples of High severity reports include but are not limited to: Issues that result in the compromise of a targeted account/s that are impractical at scale (excluding distributed brute force against accounts password/TOTP), Stored or reflected XSS that can be exploited without user interaction, False top-up vulnerabilities identified in crypto deposit processes, Manipulation of a single users account balances
`Medium`	Examples of reports eligible for a Medium bounty include but are not limited to: Disclosure of current user account/wallet balances, XSS issues that cannot be exploited without user interaction
`Low`	Examples of reports eligible for a Low bounty include but are not limited to: Valid/Theoretical vulnerabilities that require unlikely circumstances, Issues that result in inconvenience to CoinSpot Staff or Customers with limited security impact (i.e. locking a valid user out of their account)

The payouts listed by tier are the minimum bounties for valid, reproducible reports of each severity. Please be aware that during triage and investigation into reports, existing mitigations will be evaluated to determine the residual risk for the reported issue. These mitigations, along with limitations will be evaluated to determine the report severity and therefore resulting bounty.

Special bounties of $350,000 will, at CoinSpots discretion, be awarded for exceptional reports and the identification of new, high impact weaknesses affecting our platform or underlying technology. Researchers increase their chances of being awarded special bounties by submitting clear, high quality reports with step-by-step instructions on how to reproduce the identified issue. Additionally detailed descriptions of possible impacts of the weakness, along with timely responses to the CoinSpot staff and HackerOne Triage team will be viewed favourably.

Response Targets

CoinSpot will make a best effort to meet the following response targets for hackers participating in our program:

Time to first response (from report submit) - 5 days

Time to triage (from report submit) - 10 days

Time to bounty (from triage) - 14 days

We’ll try to keep you informed about our progress throughout the process.

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.

When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).

Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

Social engineering (e.g. phishing, vishing, smishing) and Attacks against our customer accounts are 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 the explicit permission of the account holder.

All Hackers must follow the rules outlined in the HackerOne Code of Conduct

Out of scope vulnerabilities

Closure of accounts with no transaction history

Enablement of 2FA without email confirmation

Reports of publicly leaked account credentials

Attacks requiring MITM or physical access to a user's device.

Rate limiting or bruteforce issues on non-authentication endpoints

Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

Upload of malicious files via s3 pre-signed URLs where impact cannot be demonstrated.

Known vulnerable versions of libraries or components without a working Proof of Concept.

Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

Severity Assessment Guidelines:

The following section provides a guide on how CoinSpot determines the criticality of reported issues.

Severity	Assessment Guidelines
`Critical`	Issues with a Critical severity rating are practically exploitable by an attacker with the impact of significant loss of funds or significant impacts to the confidentiality and integrity of CoinSpot customer data. For example: Remote command execution on a CoinSpot managed system, Access to funds (digital or fiat) outside of the context of a given user, Mass unauthorised access/modification of sensitive data
`High`	Examples of High severity reports include but are not limited to: Issues that result in the compromise of a targeted account/s that are impractical at scale (excluding distributed brute force against accounts password/TOTP), Stored or reflected XSS that can be exploited without user interaction, False top-up vulnerabilities identified in crypto deposit processes, Manipulation of a single users account balances
`Medium`	Examples of reports eligible for a Medium bounty include but are not limited to: Disclosure of current user account/wallet balances, XSS issues that cannot be exploited without user interaction
`Low`	Examples of reports eligible for a Low bounty include but are not limited to: Valid/Theoretical vulnerabilities that require unlikely circumstances, Issues that result in inconvenience to CoinSpot Staff or Customers with limited security impact (i.e. locking a valid user out of their account)