Ember EVM Smart Contracts

Bug bounty Triaged by HackenProof Ember EVM Smart Contracts: Program info Ember EVM Smart Contracts Company: Ember Protocol Scope Review: 317397 Submissions: 410 Total rewards: $0 Reputation 150 points required KYC Required PoC Required Program is: active now Live Submit report Program info Hackers 161 Reports 0 One vault platform powering all strategies One liquidity layer connecting Web2 and Web3 One brand driving the next wave of tokenized assets This is Ember Protocol. Everything Vaults. Everything Liquidity. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://github.com/ember-protocol/Ember-Vaults-EVM Copy !! Only smart contracts residing in the "contracts" folder are in scope. Additionally, the folders "test" and "testing" along with other functions/files which are intended for testing purposes are not in scope !! Please contact our support team in Discord to get access to scope. │ Smart Contract │ Critical Focus Area IN SCOPE VULNERABILITIES: Smart Contracts We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality: Stealing or loss of funds Unauthorized transaction Transaction manipulation Attacks on logic (behavior of the code is different from the business description) Reentrancy Reordering Over and underflows OUT OF SCOPE VULNERABILITIES: Smart Contracts Theoretical vulnerabilities without any proof or demonstration Old compiler version The compiler version is not locked Vulnerabilities in imported contracts Code style guide violations Redundant code Gas optimizations Best practice issues Vulnerabilities that can be exploited through front-run attacks only Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic Make every effort not to damage or restrict the availability of products, services, or infrastructure Avoid compromising any personal data, interruption, or degradation of any service Don’t access or modify other user data, localize all tests to your accounts Perform testing only within the scope Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam Don’t spam forms or account creation flows using automated scanners In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity. Don’t break any law and stay in the defined scope Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission All communication regarding the program must take place exclusively through the HackenProof platform. Contacting the project team directly through support channels, social media, or any other external communication channels is strictly prohibited. Researchers who violate this rule may be disqualified from the program and may face account suspension. Eligibility and Coordinated Disclosure We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward: You must be the first reporter of a vulnerability. The vulnerability must be a qualifying vulnerability. Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary. You must not be a former or current employee of us or one of its contractor. ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded). Provide detailed but to-the point reproduction steps. AI-generated reports without runable PoC are not accepted under this program. Disclosure Guidelines Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization. No vulnerability disclosure, including partial is allowed for the moment. Platform-Only Disclosure: Disclosure is only possible through the HackenProof Disclosure function. Researchers may request disclosure (Limited or Full) within the report ticket; We reserve the right to approve, redact, or deny disclosure requests at our sole discretion. Mutual Required: Any publication requires explicit mutual agreement. Reports must remain Private until the status is officially changed to "Public" on the HackenProof platform by the team. Live since 12 Mar 2026 Published date 12 Mar 2026 Last updated 17 Oct 2026 Range of bounty $5,000 - $15,000 Severity Critical $10,000 - $15,000 High $5,000 Medium $0 Low $0 DeFi smart contract Solidity @MrOwl KYC Verified 1 @0xelixer KYC Verified 2 @KhomDev KYC Verified 3 @IamSalted KYC Verified 4 @Ekene KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d