Triaged by Immunefi
PoC Required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$50,000Minimum reward to discourage security researchers from withholding a bug report:
$10,000Infrastructure related to card processing includes many third-party vendors including Visa, Mastercard, processors, and fraud-risk engines which protect the related infrastructure.
Attacks on those third-party systems are out-of-scope, but any attack that bypasses fraud/risk checks, that are not caught by these fraud/risk systems, would be considered in-scope.
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 $50,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 $10,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
For critical web and applications vulnerabilities, reports will be eligible for a reward of up to $50,000. Many card vulnerabilities are mitigated at daily settlement with merchant, so any and all attacks related to user spending and infrastructure must focus on impact and must demonstrate:
-
loss of funds resulting from an attack that does not require user interaction or consent, collusion with a merchant or using that merchant to generate fraudulant transactions, and must result in unauthorized transfer of funds, misdirection of funds, unbounded spending beyond limits even following daily settlement, or exposure of transactional keys or encryption keys.
-
Infrastructure breaches exposing cryptographic secret keys, personally identifiable information (PII) of multiple users beyond the reporter's own record, or scenarios enabling unauthorized spend or loss of funds affecting the platform or a user other than the currently authenticated individual.
-
Unauthorized leakage of private keys or private key generation mechanisms, leading to direct access and compromise of user funds.
-
Unbounded loss/spend of funds resulting from transactions which bypass internal controls , merchant controls, and card/processor controls which over-spend users unsettled funds beyond daily acceptable risk threadsholds that are not detected by fraud or risk systems.
All other impacts that would be classified as Critical would be rewarded a flat amount of $5,000. The rest of the severity levels are paid out according to the Impact in Scope table.
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.
- The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every [300 blocks] the attack needs for subsequent attacks from the first attack, rounded down.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties - when available on the platform - are rewarded within a range of $5,000 to $10,000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward.
Program Overview
Baanx is a global leader in fintech payments and digital assets, specialising in crypto-as-a-service.
For more information about Baanx, please visit https://www.baanx.com/.
Baanx provides rewards in USDT on ETH, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
Primacy of Impact vs Primacy of Rules
Baanx adheres to the Primacy of Impact for the following impacts:
- Smart Contract — Critical
- Smart Contract — High
- Website & Application — Critical
- Website & Application — High
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.
For more information, please see Best Practices: Primacy of Impact
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.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program(.
Known Issues
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 2: Notice Required
Prohibited Activities
- 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
Feasibility Limitations
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.