CertiK LogoCertiK Logo
Maple Finance logo
Maple Finance
Token
DeFi
Lending & Borrowing
Max Payout
$500,000
Project Overview

Maple Finance is a next-generation institutional asset management platform that bridges DeFi transparency with traditional financial sophistication. Since 2021, Maple has offered secured lending, structured products, and institutional staking—all verifiable on-chain. With the 2024 launch of the SYRUP token, Maple empowers its community through staking, governance, and protocol-driven growth, leading the evolution of institutional credit markets in decentralized finance.

Rewards by Severity

Program Overview Maple Finance offers a structured bug bounty program designed to identify and mitigate vulnerabilities in both its smart contracts and frontend infrastructure. The program is part of Maple’s commitment to platform security and transparency.

Reward Structure Rewards follow a 4-tier severity model, varying by the criticality of the issue and the type of asset affected (smart contracts or web applications). For critical smart contract vulnerabilities, rewards are capped at 10% of potential economic damage, with a minimum payout of $50,000 and a maximum of $500,000. Considerations such as brand and PR impact may influence final reward amounts at the discretion of the team.

Submission Requirements All reports must include a functional proof of concept (PoC) that demonstrates real impact on an in-scope asset. Submissions without executable code or with only theoretical analysis will not be considered eligible for a reward.

Payouts Rewards are denominated in USD and are distributed directly by the Maple team. Payouts are made in either USDC or MPL tokens, depending on Maple’s discretion.

Smart Contract
The bounty will be paid out in USD
Assets In-Scope
Target
Severity
Name
Smart Contract
WithdrawalManagerImplementation (v100)
Smart Contract
WithdrawalManagerInitializer (v100)
Smart Contract
LoanManager ( Fixed-Term for reference)
Smart Contract
WithdrawalManager (For reference)
Smart Contract
PoolDelegateCover (For reference)
Smart Contract
LoanManager (Open-Term For reference)
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of any user funds - whether at-rest or in-motion - other than unclaimed yield
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Protocol insolvency
Miner-extractable value (MEV)
Major
Faulty usage of proxy patterns
Minor price manipulation
Temporary denial of services
Temporary freezing of funds for any amount of time
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Unintended changes in smart contract permissioning
Unintended changes in proxy/upgradeability functionality
Unfair liquidations of collateral
Medium
Unexpected logic executions (doesn’t lose value)
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Weak random sources
Low
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Best practice critiques
Sybil attacks
Centralization risks
Best practice critiques
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks.
  • Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
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.
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
  • Social engineering (e.g. phishing, vishing, smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope35
Live SinceOct 3, 2023
Last Updated2mo 13d ago
Funds Reserved$500,000
Max Payout$500,000
Skynet Score
93.16
AAA
KYC
Required
PoC
Required