USDT0-logo

USDT0

USDT0 acts as a one stop solution for USDT’s interoperability and expansion to new chains. At the heart of USDT0 is LayerZero’s Omnichain Fungible Token (OFT).

Defi
Infrastructure
Stablecoin
Crosschain Liquidity
Typescript
Solidity
Maximum Bounty
$6,000,000
Live Since
30 January 2025
Last Updated
28 July 2025
  • Triaged by Immunefi

  • PoC Required

  • KYC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - USDT0 Unichain
Added on
16 July 2025
Target
Type
Smart Contract - USDT0 HyperEVM (HyperliquidExtension)
Added on
16 July 2025
Target
Type
Smart Contract - OApp Flare
Added on
16 July 2025
Target
Type
Smart Contract - OApp HyperEVM
Added on
16 July 2025
Target
Type
Smart Contract - OApp Unichain
Added on
16 July 2025
Target
Type
Smart Contract - OApp Rootstock
Added on
16 July 2025
Target
Type
Smart Contract - USDT0 Berachain
Added on
16 July 2025
Target
Type
Smart Contract - OApp Optimism
Added on
16 July 2025
Target
Type
Smart Contract - USDT0 Corn
Added on
16 July 2025
Target
Type
Smart Contract - USDT0 Rootstock
Added on
16 July 2025
Target
Type
Smart Contract - USDT0 Sei
Added on
16 July 2025
Target
Type
Smart Contract - USDT0 Flare
Added on
16 July 2025

Impacts in Scope

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Protocol insolvency

Severity
Critical
Title

Permanent freezing of funds

Severity
Medium
Title

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Out of scope

Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers