NFTfi-logo

NFTfi

NFTfi is the leading liquidity protocol for NFTs. NFTfi allows NFT owners to use the assets (NFTs) they own to access the liquidity they need by receiving secured loans from liquidity providers, peer-to-peer, in a completely trustless manner.

ETH
Defi
NFT
Lending
Solidity
Maximum Bounty
$20,000
Live Since
25 August 2023
Last Updated
05 November 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - TokenUtilityAccounting
Added on
19 March 2024
Target
Type
Smart Contract - MerkleDistributor(S2)
Added on
19 March 2024
Target
Type
Smart Contract - MerkleDistributor(S1)
Added on
19 March 2024
Target
Type
Smart Contract - MerkleDistributor(OG)
Added on
19 March 2024
Target
Type
Smart Contract - ExternalTokenLock
Added on
19 March 2024
Target
Type
Smart Contract - DistributorTokenLock
Added on
19 March 2024
Target
Type
Smart Contract - DistributorRegistry
Added on
19 March 2024
Target
Type
Smart Contract - NFTfiToken
Added on
19 March 2024
Target
Type
Smart Contract - DirectLoanOffer
Added on
25 August 2023
Target
Type
Smart Contract - DirectLoanCollectionOffer
Added on
25 August 2023

Impacts in Scope

Severity
Critical
Title

Direct theft of any user NFTs inside escrow in the loan contract

Severity
Critical
Title

MerkleDistributors should not allow claims to the locking contract for addresses and amounts not specified in the MerkleRoot (note: funds can be drained by the contract owner at any time)

Severity
Critical
Title

TokenLock contracts should not allow funds to be withdrawn to addresses that did not lock the funds

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