Lucky Lion

Lucky Lion, is the latest addition to our portfolio of APAC's leading iGaming brands with over 200,000 loyal monthly active users, allowing players to yield their tokens on our decentralised yield farm, play industry leading games and stake their winnings through the revenue sharing pool to earn even more amazing rewards.

Aiming to become the world's first community led GameFi platform built on Binance Smart Chain, we reward our loyal user-base by letting them earn up to 9% revenue share of the booming iGaming market that is expected to reach $127.3 Billion USD by 2027, at a compounding annual rate of 11.5%.

For more information about Lucky Lion, please visit https://www.luckylion.io/.

This bug bounty program is focused on their smart contracts and website and is focused on preventing the following impacts:

• Theft of governance funds
• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Thefts and freezing and modifying of gaming credit of any amount
• Thefts and freezing and modifying of revenue sharing pool of any amount

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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 Critical and High bug reports are required to have a PoC and a suggestion for a fix in order to receive a reward.

Theft of Yield or modifying game credit or revenue sharing pool is considered Critical if the theft is greater than the equivalent of USD 50,000 otherwise is considered as High.

Vulnerabilities involving any bug already disclosed in this audit are not eligible for a reward.

Vulnerabilities involving any bug already disclosed in the following are not eligible for a reward:

https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-LuckyToken-v1.0.pdf

https://public.inspex.co/report/Inspex_AUDIT2021024_LuckyLion_Farm_FullReport_v1.0.pdf

https://github.com/TechRate/Smart-Contract-Audits/blob/main/September/Lucky.pdf

Payouts are handled by the Luckylion team directly and are denominated in USD. However, payouts are done in USDT or BUSD, at the discretion of the team.

Documentation of Luckylion can be found at https://docs.luckylion.io/.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts

• Theft of governance funds
• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Thefts and freezing and modifying of gaming credit of any amount
• Thefts and freezing and modifying of revenue sharing pool of any amount

Web/App

• Thefts and freezing and modifying of revenue sharing pool of any amount
• Redirected funds by address modification

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

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)
• Feature Requests
• Best Practices

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

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

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