Skip to content

Volo Smart Contracts

By NAVI Protocol Bug bounty on HackenProof

Accepting reports KYC to get paid DeFi Move Staking
Top reward
$150,000
Top severity paid
Critical
Assets in scope
1
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $150,000
for critical bugs.
Report on HackenProof
Submit through the program page.
Replies within 6 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 Reward
Critical $150,000
Response
Within 6 days First Response 6d

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

1 asset you may test.

Source code 1

  • https://github.com/Sui-Volo/volo-smart-contracts

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Volo Smart Contracts (via HackenProof)'s policy. "We" in these lines means the program, not this site.

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
  • 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

Not accepted

  • Gas Optimization
  • Gas inefficiencies in contract operations
  • Suboptimal gas usage patterns
  • Gas cost improvements
  • Code Quality & Style
  • Code formatting and style issues
  • Missing or inconsistent comments
  • Non-security related code refactoring suggestions
  • Best practice recommendations without security impact
  • Known Issues
  • Issues already reported or acknowledged by the team
  • Publicly disclosed vulnerabilities
  • Issues listed in audit reports or documentation
  • Attacks that the reporter has already exploited themselves, leading to damage
  • Theoretical vulnerabilities without proof of concept
  • Issues in third-party dependencies (unless directly exploitable in our protocol)
  • Issues requiring highly unlikely conditions or user errors
  • Economic/game theory concerns without a direct exploit path

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 Volo Smart Contracts: Program info Volo Smart Contracts Company: NAVI Protocol Scope Review: 325843 Submissions: 616 Total rewards: $11,700 Reputation 100 points required PoC Required Program is: active now Live Submit report Program info Hackers 244 Reports 0 Ultimate Onchain Structured Fund. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://github.com/Sui-Volo/volo-smart-contracts Copy Smart Contract │ Critical Focus Area Scope Low-Medium Minor vulnerabilities that affect protocol accuracy, reliability, or availability, with limited financial or operational impact. Rounding errors in interest accrual that accumulate over time Edge cases in execution that may result in partial fund loss Gas griefing attacks that make protocol operations prohibitively expensive Denial of service vulnerabilities affecting protocol availability Improper state updates that cause incorrect interest accrual or reward distribution High Significant vulnerabilities in core protocol logic or state transitions that could result in unauthorized actions or notable financial consequences, without fully compromising the protocol. Staking logic flaws that prevent proper delegation or allow unfair allocations Exchange rate calculation errors that significantly benefit suppliers unfairly Critical Severe vulnerabilities leading to direct financial loss, unauthorized fund access, or complete protocol compromise, allowing full control over core assets or operations. Unauthorized fund extraction that enables draining protocol treasury or user deposits Permission escalation allowing unauthorized access to admin functions (pause, upgrade, withdrawal) Direct theft of user funds Out of Scope The following issues are NOT eligible for bug bounty rewards: Gas Optimization Gas inefficiencies in contract operations Suboptimal gas usage patterns Gas cost improvements Code Quality & Style Code formatting and style issues Missing or inconsistent comments Non-security related code refactoring suggestions Best practice recommendations without security impact Known Issues Issues already reported or acknowledged by the team Publicly disclosed vulnerabilities Issues listed in audit reports or documentation Other Exclusions Attacks that the reporter has already exploited themselves, leading to damage Theoretical vulnerabilities without proof of concept Issues in third-party dependencies (unless directly exploitable in our protocol) Issues requiring highly unlikely conditions or user errors Economic/game theory concerns without a direct exploit path 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 16 Oct 2025 Published date 16 Oct 2025 Last updated 12 May 2026 Range of bounty $150 - $150,000 Severity Critical $15,000 - $150,000 High $2,500 - $15,000 Medium $500 - $2,500 Low $150 - $500 Staking DeFi Sui Ecosystem smart contract Move @I1iveF0rTh1sSh1t KYC Verified 1 @0xKillua KYC Verified 2 @CL-Lucifer KYC Verified 3 @Jesjupyter KYC Verified 4 @zelyr Verified 5 Response type Business days First Response 6d Triage Time 6d Reward Time 6d Resolution Time 14d