Babylon Labs
Bounty Range
$1,000 - $500,000
external program
Babylon Labs
[/bug-bounty/](Back to Explore)
Babylon introduces a new major utility for Bitcoin: trustless and self-custodial staking. The Babylon Bitcoin staking protocol turns Bitcoin into a stakable and slashable asset for any Proof-of-Stake systems. This allows Bitcoin HODLERs to hold their Bitcoins while earning staking rewards from the PoS systems for the slashable security they provide, in the same way as how native PoS token staking works.
Bitcoin Infrastructure Staking Go Typescript JavaScript Rust
Maximum Bounty $500,000 Live Since 16 September 2024 Last Updated 28 January 2026
Triaged by Immunefi
PoC Required
KYC required
Arbitration enabled
[https://bugs.immunefi.com/dashboard/new-submission?utm_source=immunefi](Submit a Bug)
/bug-bounty/ /bug-bounty/babylon-labs/information/#top/bug-bounty/babylon-labs/scope/#top/bug-bounty/babylon-labs/resources/#top
Babylon Labs provides rewards in USDC/BABY on Ethereum/Babylon, denominated in USD.
Blockchain/DLT Critical Max: $500,000Min: $20,000
Primacy of Impact
High Max: $15,000Min: $6,000
Primacy of Impact
Medium Max: $5,000Min: $1,300
Primacy of Impact
Low Flat: $1,000 Primacy of Impact
Critical Reward Calculation Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$500,000 Minimum reward to discourage security researchers from withholding a bug report:
$20,000
The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted.
Websites and Applications Critical Max: $70,000Min: $10,000
Primacy of Impact
High Up to: $7,500 Primacy of Impact
Medium Flat: $3,000 Primacy of Impact
Low Flat: $1,000 Primacy of Impact
Rewards Body
Reward Calculation for Blockchain/DLT Critical Level Reports
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward USD 500 000. However, a minimum reward of USD 20 000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
All other impacts that would be classified as Critical would be rewarded with a minimum of USD 20 000. The rest of the severity levels are paid out according to the Impact in Scope table.
Reward Calculation for Blockchain/DLT High Level Reports
Reward Calculation for Web/Apps Critical Level Reports
For critical web/apps bug reports will be rewarded with USD 100 000, only if the impact leads to:
A loss of funds involving an attack that does not require any user action
Users funds being permanently inaccesible involving an attack that does not require any user action
Unauthorized access to user funds due to a cryptographic or key management vulnerability
All other impacts that would be classified as Critical would be rewarded with a minimum of USD 10 000.
The rest of the severity levels are paid out according to the Impact in Scope table.
Reward Payment Terms
Payouts are handled by the Babylon Labs team directly and are denominated in USD. However, payments are done in USDC on Ethereum, BABY on Babylon Genesis or a mix as determined by Babylon Labs in its sole discretion. If payment or part of the payment is in BABY tokens the conversion price for the purposes of calculation shall be determined based on the arithmetic average of the daily closing prices of the BABY token over the immediately preceding fourteen (14) calendar days before the date of payment. The daily closing price for each day during the calculation period shall be obtained from the publicly available data published on Coingecko (https://www.coingecko.com/en/coins/babylon/historical_data?utm_source=immunefi). Babylon Labs shall perform the calculation in its sole but reasonable discretion.
[/bug-bounty/babylon-labs/scope/#impacts]( View impacts in scope)
Babylon introduces a new major utility for Bitcoin: trustless and self-custodial staking. The Babylon Bitcoin staking protocol turns Bitcoin into a stakable and slashable asset for any Proof-of-Stake systems. This allows Bitcoin HODLERs to hold their Bitcoins while earning staking rewards from the PoS systems for the slashable security they provide, in the same way as how native PoS token staking works.
Phase 2 of Babylon marks the launch of Babylon Genesis, our Cosmos SDK-based chain.This includes complete feature implementation on the Babylon node (slashing and rewards), dashboard and API services, scalable infrastructure deployments, staker registration, Finality Providers coordination, and wallet support.
For more information about Babylon Labs Ltd. (“Babylon Labs”), please visit https://babylonlabs.io/?utm_source=immunefi
Babylon Labs provides rewards in USDC on Ethereum and BABY on Babylon Genesis, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section.
This bug bounty program will have a hard cap of USD $3,000,000. If multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis until that cap is reached.
KYC Requirement
Babylon Labs will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Full name
Date of birth
Proof of address (either a redacted bank statement with address or a recent utility bill)
Copy of Passport or other Government issued ID
Additional or alternate KYC information may be required by Babylon Labs or its KYC services provider. If you are an entity, KYB information will be required. Security researchers will need to provide accurate and complete information in response to each such KYC or KYB request.
Primacy of Impact vs Primacy of Rules
Babylon Labs adheres to the Primacy of Impact for the following impacts:
Blockchain/DLT - Critical
Web/App - Critical
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 [https://immunefisupport.zendesk.com/hc/en-us/articles/12340245635089-Best-Practices-Primacy-of-Impact?utm_source=immunefi](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.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the [https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules?utm_source=immunefi](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.
Anything included as an open issue in the GitHub repositories.
A staker intentionally setting a very low Bitcoin fee, might find their transaction stuck in the mempool or included in a Bitcoin block where different staking parameters apply.
Previous Audits
Babylon Labs’ completed audit reports can be found on our documentation https://docs.babylonlabs.io/guides/security/audit_reports/?utm_source=immunefi. Any vulnerabilities mentioned in these reports, fixed or unfixed, are not eligible for a reward.
Immunefi Standard Badge
By adhering to Immunefi’s best practice recommendations, Babylon Labs has satisfied the requirements for the [https://immunefisupport.zendesk.com/hc/en-us/articles/15006865432209?utm_source=immunefi](Immunefi Standard Badge).
Additional Terms
As a condition of your participation in Babylon Labs Bug Bounty Programs, including the submission of bug reports, you agree to be bound by the following terms and conditions in addition to any other terms and conditions that govern your participation. If you do not agree to these terms and conditions, you should not submit any bug report.
Babylon Labs will determine the severity level and impact for each submission, whether any submission is within scope and eligible for a reward, and the amount of a reward within a stated range, in its reasonable discretion.
Babylon Labs is not liable or responsible for any costs, fees, or expenses incurred by you in connection with this Bug Bounty Program. You acknowledge and agree that you shall be solely and exclusively responsible for the payment of any and all taxes, levies, duties, or similar governmental charges (collectively, "Taxes") that may arise in connection with any reward payments made to you. However, Babylon Labs may be required by applicable law to withhold or deduct any Taxes from payments.
Babylon Labs is an express third-party beneficiary of the Security Researchers Terms & Conditions between you and Immunefi, and entitled to enforce the terms and conditions therein as if it were an original contracting party. Babylon Labs is the party designated to be the transferee of intellectual property rights under Section 7 of the Security Researchers Terms & Conditions.
Babylon Labs, its affiliates and licensors, and their respective directors, officers, and employees (collectively, “Babylon Parties”) will have no liability arising from or relating to your use of, or conduct in connection with this Bug Bounty Program or the Immunefi platform, other than Babylon Labs’ potential obligations to pay you a reward. To the fullest extent permitted by applicable law, under no circumstances will any Babylon Parties be responsible or liable under any theory of liability, whether based in tort, contract, negligence, strict liability, warranty, or otherwise: (a) for any direct, indirect, exemplary, special, punitive, incidental, or consequential losses or damages of any kind, including without limitation, loss of profits arising from or relating to the bug bounty program or your use of the Immunefi platform. The foregoing limitations apply even if Babylon Parties were advised of or should have known of the possibility of such losses or damages and notwithstanding any failure of essential purpose of any limited remedy. The foregoing limitations will apply even if the above stated remedy fails of its essential purpose. Some jurisdictions do not allow the limitation or exclusion of certain liabilities, and damages. Accordingly, some of the disclaimers and limitations set forth in this Agreement may not apply in full to you, but will apply to the fullest extent as permitted by applicable law.
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
Default 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
[https://immunefi.com/rules/](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.
[https://immunefisupport.zendesk.com/hc/en-us/articles/19430444320401-Pre-Impact-Bug-Monitoring?utm_source=immunefi](Pre-Impact Bug Monitoring)
[https://immunefisupport.zendesk.com/hc/en-us/articles/17243068885265-Attack-Investment-Amount?utm_source=immunefi](Attack Investment Amount)
[https://immunefisupport.zendesk.com/hc/en-us/articles/17454897136401-Attacks-With-A-Financial-Risk-To-The-Attacker?utm_source=immunefi](Attacks With A Financial Risk To The Attacker)
[https://immunefisupport.zendesk.com/hc/en-us/articles/17455102268305-When-Is-An-Impactful-Attack-Downgraded-To-Griefing?utm_source=immunefi](When Is An Impactful Attack Downgraded To Griefing?)
[https://bugs.immunefi.com/dashboard/new-submission?utm_source=immunefi](Submit a Bug) [/bug-bounty/babylon-labs/scope/#assets](Total Assets in Scope17 )