Hydration-logo

Hydration

Hydration is the leading liquidity protocol on Polkadot. Its mission is to make DeFi efficient, simple, and unstoppable. To achieve this, Hydration unites swaps, lending and a stablecoin currency under the roof of a single, scalable appchain.

Polkadot
Blockchain
Defi
AMM
DEX
Staking
Rust
Maximum Bounty
$1,000,000
Live Since
20 February 2023
Last Updated
11 June 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Added on
Blockchain/DLT - EVM precompiles
21 May 2024
Target
Type
Added on
Blockchain/DLT - EVM precompiles
21 May 2024
Target
Type
Added on
Blockchain/DLT - EVM precompiles
21 May 2024
Target
Type
Added on
Websites and Applications - repo #2
19 March 2024
Target
Type
Added on
Websites and Applications - repo #1
19 March 2024
Target
Type
Added on
Blockchain/DLT - traits lib
19 March 2024
Target
Type
Added on
Blockchain/DLT - XYK Math
19 March 2024
Target
Type
Added on
Blockchain/DLT - pallet-xyk
19 March 2024
Target
Type
Added on
Blockchain/DLT - pallet-xyk
19 March 2024
Target
Type
Added on
Blockchain/DLT - pallet-xyk
19 March 2024
Target
Type
Added on
Blockchain/DLT - pallet-xyk
19 March 2024
Target
Type
Added on
Blockchain/DLT - Rate Limiter Math
19 March 2024

Impacts in Scope

Critical
Governance compromise
Critical
Identity theft that compromises user’s assets (fungible, non-fungibles)
Critical
Unauthorized token minting
Critical
Unauthorized NFT minting
Critical
Omnipool account theft
Critical
Omnipool manipulation resulting in loss/theft of liquidity
Critical
Double spending
Critical
Direct loss of funds
Critical
Transaction/consensus manipulation
Critical
Direct theft of user’s assets (fungibles, non-fungibles)
Critical
Performing state modifying action without user’s consent such as making trades, transfers, withdrawals etc.
Critical
Subdomain takeover (only applies to main Hydration web app)

Out of scope

Program's Out of Scope information

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)

Smart Contracts and Blockchain

  • Incorrect data supplied by third-party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks
  • Centralization risks

Websites and Apps

  • 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 ex: 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 (ex: 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 ex: etherscan, Infura, Alchemy, etc.
  • Any vulnerability exploit which requires browser bugs for exploitation. ex: CSP bypass

The following activities are prohibited by this bug bounty program:

  • Any testing with mainnet or public testnet; 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