Hashflow

Submit a Bug
29 March 2022
Live since
No
KYC required
$40,000
Maximum bounty
13 October 2022
Last updated

Program Overview

Hashflow is the most powerful DeFi trading experience that gives you tight spreads, zero slippage and MEV-resistance.

For more information about Hashflow, please visit https://www.hashflow.com/.

This bug bounty program is focused on their website and app, and is focused on preventing:

  • Ability to execute system commands
  • Extract Sensitive data/files from the server such as /etc/passwd
  • Stealing User Cookies
  • Taking Down the application/website
  • Bypassing Authentication
  • Signing transactions for other users
  • Redirection of user deposits and withdrawals
  • Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
  • Wallet interaction modification resulting in financial loss
  • Direct theft of user funds
  • Tampering with transactions submitted to the user’s wallet
  • Submitting malicious transactions to an already-connected wallet

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Payouts are handled by the Hashflow team directly and are denominated in USD. However, payouts are done in USDC, USDT and DAI, with the choice of the ratio at the discretion of the team.

Websites and Applications

Critical
Level
USD $40,000
Payout
PoC Required
High
Level
USD $20,000
Payout
PoC Required
Medium
Level
USD $5,000
Payout
PoC Required
Low
Level
USD $2,000
Payout
PoC Required

Assets in scope

Impacts in scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Websites and Applications

  • Ability to execute system commands
    Critical
    Impact
  • Extract Sensitive data/files from the server such as /etc/passwd
    Critical
    Impact
  • Stealing User Cookies
    Critical
    Impact
  • Bypassing Authentication
    Critical
    Impact
  • Taking Down the application/website
    Critical
    Impact
  • Redirection of user deposits and withdrawals
    Critical
    Impact
  • Signing transactions for other users
    Critical
    Impact
  • Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
    Critical
    Impact
  • Direct theft of user funds
    Critical
    Impact
  • Wallet interaction modification resulting in financial loss
    Critical
    Impact
  • Submitting malicious transactions to an already-connected wallet
    Critical
    Impact
  • Tampering with transactions submitted to the user’s wallet
    Critical
    Impact
  • Spoofing content on the target application (Persistent)
    High
    Impact
  • Users Confidential information disclosure such as Email
    High
    Impact
  • Subdomain Takeover without financial loss (applicable for subdomains with no addresses published)
    High
    Impact
  • Privilege escalation to access unauthorized functionalities
    High
    Impact
  • Changing details of other users without direct financial impact (CSRF)
    Medium
    Impact
  • Third-Party API keys leakage that demonstrates loss of funds or modification on the website
    Medium
    Impact
  • Redirecting users to malicious websites (Open Redirect)
    Medium
    Impact
  • Framing sensitive pages leading to financial loss (ClickJacking)
    Low
    Impact
  • Broken Link Hijacking
    Low
    Impact
  • Any impact involving a publicly released CVE without a working PoC
    Low
    Impact

Out of Scope & Rules

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)

Websites and Apps

  • Theoretical vulnerabilities without any proof or demonstration
  • Content spoofing / Text injection issues
  • Self-XSS
  • Captcha bypass using OCR
  • CSRF with no security impact (logout CSRF, change language, etc.)
  • Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
  • Server-side information disclosure such as IPs, server names, and most stack traces
  • Vulnerabilities used to enumerate or confirm the existence of users or tenants
  • Vulnerabilities requiring unlikely user actions
  • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization
  • Feature requests
  • Best practices
  • Vulnerabilities primarily caused by browser/plugin defects
  • Any vulnerability exploit requiring CSP bypass resulting from a browser bug

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 our 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