Swap.io Smart Contracts: Program info

IN SCOPE VULNERABILITIES (Smart Contracts)

Critical

• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
• Permanent freezing of funds
• Vulnerabilities that could freeze user funds permanently or involve the draining or theft of funds without user transaction approval

High

• Theft of unclaimed yield
• Permanent freezing of unclaimed yield
• Temporary freezing of funds for any amount of time
• Vulnerabilities that could freeze user funds temporarily or intentionally alter the value of user funds

Medium

• Smart contract unable to operate due to lack of token funds
• Block stuffing for profit
• Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
• Theft of gas
• Unbounded gas consumption

OUT OF SCOPE VULNERABILITIES (Smart Contracts)

• Attacks that the reporter has already exploited themselves, leading to damage
• Theoretical vulnerabilities without any proof or demonstration
• Old compiler version
• The compiler version is not locked
• Vulnerabilities in imported contracts
• Attacks requiring access to leaked keys/credentials
• Code style guide violations
• Redundant code
• Gas optimizations
• Best practice issues
• Vulnerabilities that can be exploited through front-run attacks only
• Incorrect data supplied by third party oracles (not excluding oracle manipulation/flash loan attacks)
• Impacts requiring basic economic and governance attacks (e.g. 51% attack)
• Attacks requiring access to privileged addresses (governance, strategist)
• Lack of liquidity impacts
• Impacts from Sybil attacks
• Impacts involving centralization risks
• MEV vectors the swap.io or Raydium teams are already aware of
• The CLMM contract emits trading fee and farming yield tokens to LPs. If tokens from the vault or fees were drained by an attacker however, users would not be able to claim yield and transactions would fail. This is by design and not a vulnerability.
• Bugs previously fixed by the Raydium team

• All bounty submissions must be accompanied by a Proof-of-Concept (PoC).
• 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
• 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

• 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