Gala Games

The decentralized Gala Games entertainment ecosystem uses web3 to allow user ownership of tokens and in-game items. Because cryptocurrency wallets and digital asset ownership are part of the Gala Games experience, security is of utmost importance.

For more information about Gala Games entertainment ecosystem, please visit https://gala.com/.

Gala Games provides bounty rewards in $GALA. For more details about the payment process, please view the Rewards by Threat Level section further below.

KYC Requirement

The provision of KYC and KYT is required to receive a reward for this bug bounty program, where the following information will be required to be provided:

• Identity Proof (Passport, / National ID).
• Legitimacy of the wallet on which they would like to receive their bounty payment.

KYC and KYT information is only required on confirmation of the validity of a bug report and is mandatory to be eligible for a bug bounty payout.

Responsible Publication

Gala Games adheres to category 3. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

Primacy of Impact vs Primacy of Rules

Gala Games adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.

Restrictions on Security Researcher Eligibility

Security researchers who fall under any of the following are ineligible for a reward:

• KYC blocked security researchers - Gala Games cannot pay bounties to individuals that take part in criminal or illegal activities. Therefore, Gala Games must perform KYC and wallet verification due to rules & regulations.
• KYT blocked wallets - the identity of the individual must be verified as well as the legitimacy of the wallet on which they would like to receive their bounty payment due to rules & regulations.

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• Smart contract, Critical severity
• Smart contract, High severity
• Smart contract, Medium severity
• Websites & applications, Critical severity
• Websites & applications, High severity
• Websites & applications, Medium severity

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

Reward Payment Terms

Payouts are handled by the Gala Games team directly and are denominated in USD. However, payments are done in $GALA.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. For avoidance of doubt, if the reward amount is USD 5 000 and the average price is USD 1.75 per token, then the reward will be 2857.142857 units of that token.

These impacts are out of scope for this bug bounty program.

All Categories

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
• Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
• Best practice recommendations
• Feature requests
• Impacts on test files and configuration files unless stated otherwise in the bug bounty program
• Physical or social engineering attempts (including phishing attacks)
• Ability to take over external tools or social media accounts
• Vulnerabilities that have already been reported or are already known at Gala
• Vulnerabilities caused by a lack of encryption or by using weak encryption methods
• Subdomain takeover

Smart Contracts and Blockchain/DLT

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Impacts requiring basic economic and governance attacks (e.g. 51% attack)
• Lack of liquidity impacts
• Impacts from Sybil attacks
• Impacts involving centralization risks
• Best practice recommendations

Web/App

• Theoretical impacts without any proof or demonstration
• Impacts involving attacks requiring physical access to the victim device
• Impacts involving attacks requiring access to the local network of the victim
• Reflected plain text injection (e.g. url parameters, path, etc.)
  • This does not exclude reflected HTML injection with or without JavaScript
  • This does not exclude persistent plain text injection
• Any impacts involving self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (e.g. logout CSRF)
• Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
• Impacts causing only the enumeration or confirmation of the existence of users or tenants
• Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• Impacts that only require DDoS
• UX and UI impacts that do not materially disrupt use of the platform
• Impacts primarily caused by browser/plugin defects
• Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
• Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
• SPF/DMARC misconfigured records
• Missing HTTP Headers without demonstrated impact
• Automated scanner reports without demonstrated impact
• UI/UX best practice recommendations
• Non-future-proof NFT rendering
• Vulnerabilities reported by automated tools or reports from automated web vulnerability scanners (Acunetix, Vega, etc.)
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Lack of SSL/TLS best practices or scan reports (from sites such as SSL Labs)
• CSV injection
• Protocol mismatch
• Rate limiting
• Exposed login panels
• Dangling IPs
• Reports that affect only outdated user agents or app versions
• Stack traces
• Path disclosure
• Directory listings
• Breach of our privacy statement

The following activities are prohibited by this bug bounty program:

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