Abracadabra

Abracadabra is a lending platform that uses interest-bearing tokens (ibTKNs) as collateral to borrow a USD pegged stablecoin (Magic Internet Money - MIM), that can be used as any other traditional stablecoin.

For more information about Abracadabra, please visit https://abracadabra.money/.

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

• Theft of funds inside of the cauldrons
• Crashing of the cauldrons
• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC in order to be considered for a reward. All Medium, High, and Critical Smart Contract bug reports require a PoC to be eligible for a reward.

The following vulnerabilities are not eligible for a reward:

The CauldronV1 don’t properly account for borrow opening fees

Payouts are handled by the Abracadabra team directly and are denominated in USD. However, payouts are done in ETH,USDT,SPELL,MIM, with the choice of the ratio at the discretion of the team.

Smart Contract

Websites and Applications

All smart contracts of Abracadabra can be found at https://github.com/Abracadabra-money/magic-internet-money/tree/main/contracts. All folders with “Degenbox”, “Outdated” and “BentoBoxFlat.sol” are out of scope. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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)
• Sustained price movements over minutes leading to a changed oracle price

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
• Websites and Apps
• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

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