WePiggy-logo

WePiggy

WePiggy is an open source, non-custodial crypto asset lending market protocol. In WePiggy's market, users can deposit their crypto assets to earn interest, or borrow others by paying interests.

BSC
ETH
Heco
Optimism
Polygon
Defi
NFT
Asset Management
L2
Lending
JavaScript
Solidity
Maximum Bounty
$100,000
Live Since
29 January 2022
Last Updated
29 November 2024
  • PoC Required

  • KYC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - P_WBTC
Added on
4 March 2022
Target
Type
Smart Contract - P_ETH
Added on
4 March 2022
Target
Type
Smart Contract - P_USDC
Added on
4 March 2022
Target
Type
Smart Contract - P_DAI
Added on
4 March 2022
Target
Type
Smart Contract - P_USDT
Added on
4 March 2022
Target
Type
Smart Contract - P_UNI
Added on
4 March 2022
Target
Type
Smart Contract - Timelock
Added on
4 March 2022
Target
Type
Smart Contract - STABLECOIN_JUMP_RATE_MODEL
Added on
4 March 2022
Target
Type
Smart Contract - COMPTROLLER
Added on
4 March 2022
Target
Type
Smart Contract - P_YFII
Added on
4 March 2022
Target
Type
Smart Contract - P_LRC
Added on
4 March 2022
Target
Type
Smart Contract - P_RAI
Added on
4 March 2022

Impacts in Scope

Severity
Critical
Title

Loss of user funds staked (principal) by freezing or theft

Severity
Critical
Title

Loss of governance funds

Severity
Critical
Title

Shell access on server

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Freezing of unclaimed yield for at least 24 hours

Out of scope

Program's Out of Scope information
  • Best practice critiques
  • Attacks requiring privileged access from within the organization
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