deBridge-logo

deBridge

deBridge is a cross-chain interoperability and liquidity transfer protocol that allows decentralized transfer of data and assets between various blockchains. The deBridge protocol is an infrastructure platform and hooking service for:

Arbitrum
Avalanche
BSC
ETH
Fantom
Heco
Polygon
Defi
Infrastructure
Bridge
Crosschain Liquidity
DEX
Solidity
Maximum Bounty
$200,000
Live Since
21 January 2022
Last Updated
08 April 2024
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Critical
USD $200,000 and unique deBridge NFT
High
USD $40,000
Medium
USD $5,000

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.

In addition to Immunefi’s Vulnerability Severity Classification System, deBridge classifies the following vulnerabilities as follows. In case of discrepancy, the one below will be followed.

Critical

  • More than 5% of the loss of TVL or an unauthorized minting of deAssets in an amount that leads to substantial loss of the peg of the wrapped asset (Total supply of deAsset exceeds amount of underlying collateral locked for more than 5%)

High

  • Up to 5% of the loss of TVL or an unauthorized minting of deAssets in an amount that leads to substantial loss of the peg of the wrapped asset (Total supply of deAsset is on up to 5% exceeds the amount of underlying collateral locked)

The following vulnerabilities/problems are not eligible for a reward:

  • Default bridging functionality doesn’t support non-standard assets (e.g. rebase assets, assets with elastic supply or tokens with fees during transfer)
  • If a user sets an incorrect receiver or fallback address he won’t be able to claim his transfer in the destination chain and funds might be locked forever
  • If user passes ​​REVERT_IF_EXTERNAL_FAIL flag and specifies "data" and "receiver address" params that will lead to tx being constantly reverted
  • Framework used by the deBridge node exploitation of which requires knowledge of IP address unless information about IP address was obtained during the attack
  • Problem with the callProxy smart contract when gas limit specified by claimer is not enough for the proper execution of the externalCall that leads to externalCall being reverted even though transaction itself is completed

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

Program Overview

deBridge is a cross-chain interoperability and liquidity transfer protocol that allows decentralized transfer of data and assets between various blockchains. The deBridge protocol is an infrastructure platform and hooking service for:

  • cross-chain composability of smart contracts
  • cross-chain swaps
  • bridging of any arbitrary asset and data
  • interoperability and bridging of NFTs

More information about the project can be also found in the documentation portal or at the website https://debridge.finance/.

Examples of how users can interact with the protocol from the command line can be found in the repository: https://github.com/debridge-finance/debridge-contracts-v1/tree/main/examples.

Status of transactions can be tracked through the deBridge explorer.

This bug bounty program is focused on their smart contracts and is focused on preventing:

  • Loss of user funds locked (principal) by freezing or theft
  • Loss of governance funds
  • Theft of unclaimed assets
  • Permanent freezing of unclaimed assets
  • Smart contract fails to deliver promised returns
  • Unauthorized minting of wrapped assets that will lead them to loosing peg

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

Default prohibited activities
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • 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 that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty
  • Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.