Babylon is a community-led asset management protocol that enables users to invest in DeFi together. It's built on the Ethereum network and it's non-custodial, transparent, permission-less, and governed by the community.
Babylon has a two-layer governance system. The protocol is managed by the holders of the governance token, BABL, which is used to vote on changes to the protocol and decide on the best use of the protocol treasury.
Babylonians can create investment communities (called "Gardens 🌴") and invite people to deposit capital. Members participate in the garden by joining the discord chat, suggesting investment Strategies and voting on Strategies which will eventually execute and receive capital automatically depending on the voting results. Members receive rewards based on their contributions and their role within the garden.
Babylon helps people build wealth and achieve financial freedom as we believe that crypto is the best asset class for the next two decades and we want to help as many people as possible get access to it through our DeFi investment clubs or gardens.
For more information about Babylon, please visit https://www.babylon.finance/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. Smart contracts bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.
Critical smart contract vulnerabilities are capped at 10% of economic damage with a maximum of 100K, only if the impact leads to a direct loss in funds. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 50 000 for valid Critical smart contract bug reports.
To determine the final reward amount in all cases, the likelihood to have a meaningful impact on availability, integrity, and/or loss of funds is considered. The final decision on the payout amount will be determined by the Babylon Finance team at its discretion.
The following vulnerabilities are not eligible for a reward:
- MEV Doom loop as reported in this article (*).
- Creating a malicious poisoned vault/strategy for a legit integration.
- All vulnerabilities marked in the security reviews are not eligible for a reward.
Payouts are handled by the Babylon team directly and are denominated in USD. However, payouts are done mainly in DAI, USDC, ETH and/or other reserve assets at the protocol Treasury, with the choice of the ratio at the discretion of the team.
- Up to USD $100,000
- USD $5,000 to USD $20,000
Websites and Applications
- Up to USD $30,000
- USD $2,000 to USD $10,000
Assets in scope
- Smart Contract - BABControllerType
- Smart Contract - Ishtar GateType
- Smart Contract - Marduk GateType
- Smart Contract - BABL TokenType
- Smart Contract - ProphetsNFTType
- Smart Contract - ProphetsArrivalType
- Smart Contract - TreasuryType
- TargetWebsites and Applications - Main Web AppType
All smart contracts of Babylon will be found at https://github.com/babylon-finance. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.
If an impact can be caused to any other asset managed by Babylon that isn’t on this table but for which the impact is in the Impacts in Scope section, you are encouraged to submit it for the consideration of the project. This applies to only Critical and High impacts.
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.
- Direct theft of user funds of equal or more than USD 500 000CriticalImpact
- Permanent freezing of funds of equal or more than USD 500 000CriticalImpact
- Miner-extractable value (MEV) (see exceptions) of equal or more than USD 500 000CriticalImpact
- Protocol InsolvencyCriticalImpact
- Any Critical impacts which funds at risk are below USD 500 000HighImpact
- Theft of funds of unclaimed mining rewardsHighImpact
- Permanent freezing of unclaimed mining rewardsHighImpact
- Temporary freezing of funds with a minimum period of 24 hoursHighImpact
Websites and Applications
- Execute arbitrary privileged / unauthorized system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames, etc)CriticalImpact
- Taking Down the application/websiteCriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, voting, claiming rewards, deposits and withdrawals, etc.CriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Direct theft of user fundsCriticalImpact
- Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.HighImpact
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
Out of Scope & Rules
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)
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
- Sandwich attacks.
- Centralization risks
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude persistent plain text injection
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- 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
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
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