Xterio
Bounty Range
$1,000 - $80,000
external program
Xterio
Established in 2022, Xterio is a Web3 gaming ecosystem & infrastructure, distinguishing itself as a gaming publisher with top-notch development skills and unparalleled distribution expertise. Xterio is driven by a bold vision – to reshape entertainment and gaming through the strength of digital collectibles. These non-fungible assets hold the power to redefine how we experience joy. By embracing the limitless potential of digital collectibles, we empower individuals to be not just spectators but active participants, collectors, and creators in dynamic virtual universes.
For more information about Xterio, please visit https://xter.io/
Xterio provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Websites and Applications
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $80,000.
Minimum reward to discourage security researchers from withholding a bug report: $50,000
All other impacts that are classified as Critical: Websites and Applications will be rewarded a flat amount of $2,500.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 80,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 50,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 20,000 to USD 50,000 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24 hours that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
For critical web/apps bug reports will be rewarded with USD 5,000, only if the impact leads to:
A loss of funds involving an attack that does not require any user action
Private key or private key generation leakage leading to unauthorized access to user funds
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 2,500. The rest of the severity levels are paid out according to the Impact in Scope table.
Reward Payment Terms
Payouts are handled by the Xterio team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
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.
Xterio provides rewards in USDC on Ethereum, denominated in USD.
KYC Requirement
Xterio will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Primacy of Impact vs Primacy of Rules
Xterio adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
Please note that, regardless of what is displayed in the Rewards table, Medium severity impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Vulnerable JS Library: The identified library nextjs, version 12.2.0 is vulnerable.
RaffleAuctionMinter and DepositRaffleMinter smart contracts use an on-chain randomness generator, which could be leveraged by potential attackers. But we believe the value of the attack is less than the cost.
The signature for WhitelistMinter.mintWithSig can be used repeatedly. It's a designed feature to allow frontend apps reuse the signature to lower signature and API calling pressure. The mint limit for each address lies on the signed array parameter - limits.
The MarketplaceV2 smart contract does not include chainId in the signature, which is because we currently do not support collections with identical addresses across different chains. We will update this together with other features in the future.
Previous Audits
Xterio's completed audit reports can be found at https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-Xterio-v1.0.pdf and https://github.com/peckshield/publications/tree/master/audit_reports/PeckShield-Audit-Report-FansCreate-v1.0.pdf
Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Immunefi Standard Badge
By adhering to Immunefi's best practice recommendations, Xterio has satisfied the requirements for the Immunefi Standard Badge.
The submission of KYC information is a requirement for payout processing.
Participants must adhere to the Eligibility Criteria.
Proof of concept is always required for all severities.
Category 3: Approval Required
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
Any other actions prohibited by the Immunefi Rules
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.