AirPuff revolutionizes the distribution and value realization from emerging Liquid Restaking and Restaking protocols, offering users an unprecedented opportunity to optimize their earnings.
In Scope
| Target | Type | Severity | Reward |
|---|---|---|---|
https://arbiscan.io/address/0x6295248F578bFA9c057a3e1182BED27121530E7AAirPuff Vault ezETH |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0x65E7C3C88806FF010BB197B2577cCddA9704fA2FAirPuff Vault rsETH |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0xb8Cfb3406aBE78a2C836DCe69608e9cD80a78301Airpuff Vault weETH |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0xa2e4cab1F6f9f1163bCe937517f1935BEc4a0A7cUSDCe Lending |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0xeb0b9B5FFb763dD69440565F63c67f9695B7C3dAUSDT Lending |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0x529f94bcd37896b6a38452497C62b2F0a8217517ARB Lending |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0x521a8ca3baf3d7677ddcc091ed91d969d4afcff8wstETH Lending |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0x97801654D2048E639043c77b16Bc906541B3490aETH Lending |
Protocol | Critical | Bounty |
https://arbiscan.io/address/0xd3E1BDe4b4163c86B9b7668dE8Ae7618720dCa93USDC Lending |
Protocol | Critical | Bounty |
https://etherscan.io/address/0x291B812D84707EEB256D618C4c333Ff5F451321FAirPuff Vault uniETH |
Protocol | Critical | Bounty |
https://etherscan.io/address/0x32a0ce2bDfc37eE606aB905b4f9fC286049A774fAirPuff Vault ezETH |
Protocol | Critical | Bounty |
https://etherscan.io/address/0xEc69AaC84D3081aA6F4636C5DBD3D7C2c2F42a9CAirPuff Vault rsETH |
Protocol | Critical | Bounty |
https://etherscan.io/address/0x5e0a74cb0F74D57F9d69914575b972ba6A14e27cAirpuff Vault weETH |
Protocol | Critical | Bounty |
https://etherscan.io/address/0xdeF3AA48bad043e53207d359dcDFdE46F50b6C02ETH Lending |
Protocol | Critical | Bounty |
IN-SCOPE: SMART CONTRACT VULNERABILITIES
We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality:
- Stealing or loss of funds
- Unauthorized transaction
- Transaction manipulation
- Attacks on logic (behavior of the code is different from the business description)
- Reentrancy
- Reordering
- Over and underflows
OUT OF SCOPE: SMART CONTRACT VULNERABILITIES
- Theoretical vulnerabilities without any proof or demonstration
- Old compiler version
- The compiler version is not locked
- Vulnerabilities in imported contracts
- Code style guide violations
- Redundant code
- Gas optimizations
- Best practice issues
- Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
- Make every effort not to damage or restrict the availability of products, services, or infrastructure
- Avoid compromising any personal data, interruption, or degradation of any service
- Don’t access or modify other user data, localize all tests to your accounts
- Perform testing only within the scope
- Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
- Don’t spam forms or account creation flows using automated scanners
- In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
- Don’t break any law and stay in the defined scope
- Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
- Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
- No vulnerability disclosure, including partial is allowed for the moment.
- Please do NOT publish/discuss bugs
We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability
- Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
- You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
- You must not be a former or current employee of us or one of its contractor.
- ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
- Provide detailed but to-the point reproduction steps