Moola

Moola is a non-custodial liquidity protocol built on the Celo blockchain that is democratizing access to yield and credit. Depositors actively earn yield which is paid for by borrowers who are able to take over-collateralized loans in perpetuity, under-collateralized credit delegated or flash loans. Moola has shared ancestry with Aave v2.

For more information about Moola, please visit https://moola.market/.

This bug bounty program is focused on their smart contracts, website and app and is focused on preventing:

• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Website goes down
• Leak of user data
• Deletion of user data
• Access to sensitive pages without authorization

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward.

Moola requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. Bug bounty hunters will need to show a government-issued ID, including a physical address.

Critical Smart Contract reward is $10,000 USD or up to 1% of MOO supply High Smart Contract reward $5,000 USD or up to 0.5% of MOO supply Critical Web/App reward is 2,000 USD or up to 0.2% of MOO supply High Web/App reward is 1,000 USD or up to 0.1% of MOO supply

Payouts are handled by the Moola team directly and are denominated in USD. However, payouts are done in cUSD or MOO at the discretion of the team. For payouts done in MOO, the price of MOO will be calculated based on a 30-day average USD price. MOO payments may incur a linear unlock period up to twelve months.

Smart Contract

Websites and Applications

All smart contracts of Moola can be found at https://github.com/moolamarket/moola-v2. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

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)

Smart Contracts and Blockchain

• 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

Websites and Apps

• 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)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by this bug bounty program:

• 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty