Kai Finance Yield Protocol
By Kai Finance Bug bounty on HackenProof
- Top reward
- $100,000
- Top severity paid
- Critical
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $100,000
- for critical bugs.
- Report on HackenProof
- Submit through the program page.
- Replies within 5 days
- As the policy promises.
- Payment
- Proof of identity needed to get paid.
- No public write-ups
- Keep findings private.
Rewards
What HackenProof lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$100,000 |
- Response
-
Within 5 days
First Response 5d
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 11 excluded.
Smart contracts 2
- 0x0d9dd55ac7eb676dc78f7d0ae3bc5529d7fd6b52ac0d0edb2d7820c52d080026 Access Management
- 0x51e0ccce48f0763f98f1cb4856847c2e1531adacada99cdd7626ab999db57523 Leverage Core
Source code 2
- https://github.com/kunalabs-io/sui-smart-contracts/tree/master/access-management
- https://github.com/kunalabs-io/sui-smart-contracts/tree/master/kai/leverage/core
Out of scope (11)
- Best practice issues
- Bugs that only affect test code or test logic without impacting production contract behavior
- Code style guide violations
- Gas optimizations
- Old compiler version
- Redundant code
- Reports on modules that are not deployed, not used in production, or not part of the listed package IDs or their valid upgrades will be considered out of scope.
- The compiler version is not locked
- Theoretical vulnerabilities without any proof or demonstration
- Vulnerabilities in imported contracts
- Vulnerabilities that can be exploited through front-run attacks only
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Kai Finance Yield Protocol (via HackenProof)'s policy.
While testing
-
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
-
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
-
Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
Not accepted
-
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
-
Bugs that only affect test code or test logic without impacting production contract behavior
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Bug bounty Triaged by HackenProof Kai Finance Yield Protocol: Program info Kai Finance Yield Protocol Company: Kai Finance Scope Review: 248381 Submissions: 462 Total rewards: $0 Reputation 50 points required PoC Required Program left: 74 days ago Finished Submit report Contest is not active Program info Hackers 245 Reports 0 Kai Finance offers innovative yield farming solutions for both passive and active investors. Whether you prefer steady, low-maintenance income or want to explore strategies with higher yield potential, our platform provides secure, transparent access to the best of DeFi. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://github.com/kunalabs-io/sui-smart-contracts/tree/master/kai/leverage/core Copy Smart Contract │ Critical https://github.com/kunalabs-io/sui-smart-contracts/tree/master/access-management Copy 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 Bugs that only affect test code or test logic without impacting production contract behavior Only the source code of live, deployed Move modules that correspond to the following original on-chain package IDs - and their upgrades - are in scope. This includes any versions deployed through a valid upgrade mechanism under the same package ID. Reports on modules that are not deployed, not used in production, or not part of the listed package IDs or their valid upgrades will be considered out of scope. In-scope Original Package IDs: 0x51e0ccce48f0763f98f1cb4856847c2e1531adacada99cdd7626ab999db57523 Leverage Core 0x0d9dd55ac7eb676dc78f7d0ae3bc5529d7fd6b52ac0d0edb2d7820c52d080026 Access Management Note: If a vulnerability existed in a previous version of a package but has already been fixed in a later upgrade, it is not eligible for a bounty. Only valid vulnerabilities affecting the currently live, deployed version of the package are in scope. 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 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 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. Please do NOT publish/discuss bugs Live since 02 Sep 2025 Published date 02 Sep 2025 Last updated 31 Aug 2026 Range of bounty $5,000 - $100,000 Severity Critical $50,000 - $100,000 High $5,000 - $10,000 Medium $0 Low $0 DeFi Sui Ecosystem smart contract Move @Zenmagnum KYC Verified 1 @shaul KYC Verified 2 @dummysui Verified 3 @Dhruva Verified 4 @az Verified 5 Response type Business days First Response 5d Triage Time 5d Reward Time 7d Resolution Time 30d