🏹Bug Bounty

We value the work of white hat hackers who help us maintain the security of our platform. As the TVL of the protocol scales, we will scale these figures upward. It is our goal to have the most favorable bug bounty to asset locked ratio in the industry. If you have a bug report reach out to a mod in our Telegram group: https://t.me/OokiTrade

Scope

This bug bounty program is focused on the prevention of negative impacts to Ooki protocol and covers smart contracts and app and is focused on preventing:

https://github.com/OokiTrade/contractsv2

• Exploits resulting in the locking, loss, or theft of user funds.

• Governance manipulation.

• Exposure of infrastructure private keys and/or PII.

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

• Permanent freezing of funds

• Insolvency

• Loss of user funds by freezing, theft, or manipulation of price

• Unable to call smart contract

• Thefts and freezing of principal of any amount

• Thefts and freezing of unclaimed yield of any amount

• Theft of governance funds

Assets in scope

Only the in the Assets in Scope table are considered as in-scope of the bug bounty program.

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability. Critical smart contract and blockchain bug reports are further distributed according to the following tier system:

• Tier 1 - Critical $50k

• Tier 2 - High $25k

• Tier 3 - Medium $5k

Submission Requirements

All smart contract and bug reports must come with log components, reproduction, and data about vulnerabilities to support learnings and bug fixes. This can be satisfied by providing relevant screenshots, docs, code, and steps to reproduce the issue.

All bug bounty hunters to complete the program’s KYC requirements if they are submitting a report and wanting a reward. The information needed is an ID photo along with a scan of a utility bill to show residency proof.

Out of Scope

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets

• 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

• Any violation of privacy of network users, other bounty hunters or Wormhole Foundation

• Automated testing of services that generates significant amounts of traffic

• Public disclosure of an unpatched vulnerability in an embargoed bounty

The following activities are prohibited by this bug bounty program:

• Theoretical vulnerabilities without any proof or demonstration

• Content spoofing / Text injection issues

• Self-XSS

• Captcha bypass using OCR

• CSRF with no security impact (logout CSRF, change language, etc.)

• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)

• Server-side information disclosure such as IPs, server names, and most stack traces

• Vulnerabilities used to enumerate or confirm the existence of users or tenants

• Vulnerabilities requiring unlikely user actions

• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)

• Framing sensitive pages leading to financial loss (ClickJacking)

• Lack of SSL/TLS best practices

• DDoS vulnerabilities

• Attacks requiring privileged access from within the organization

• Feature requests

• Best practices

Websites and Apps

• Network denial of service on Guardians is not eligible for bug bounty rewards

• Frontrunning, including backrunning and sandwich attacks.

• Incorrect data supplied by third party oracles

• Not to exclude oracle manipulation/flash loan attacks

• Basic economic governance attacks (e.g. 51% attack)

• Lack of liquidity

• Best practice critiques

• Sybil attacks

• Centralization risks

• Bugs in dependencies (unless they lead to equivalently direct attacks on Wormhole).

• Any secret data checked into the repository. Such as API/AUTH tokens.

Smart Contracts and Blockchain

• Attacks that the reporter has already exploited themselves, leading to damage

• Attacks requiring access to leaked keys/credentials

• Attacks requiring access to privileged addresses (governance, strategist)

The following vulnerabilities are not eligible for a reward:

• Exploits that require access to the Timelock admin keys or Price Feed admin keys

• Cases involving risks of losses to the pool in case the assets in the pool decrease in price

• Cases involving price manipulation on exchanges

• Exploits that are not economically practical to execute

• Exploits due to delays or sizes of price feed updates

• In general, we assume that the fees earned from swaps and leverage trading over a period of a few months will be larger than any potential losses from price updates, we will be analyzing past data to adjust the fees and parameters for this.