Status DataClose notification
Bug bounty Triaged by HackenProof

Cetus Smart Contracts: Program info

Cetus Smart Contracts

Company: Cetus

Scope Review:
345426
Submissions:
482
Total rewards:
$310
Reputation
100 points required
KYC
Required
PoC
Required

Program is: active now

Live

Cetus is a leading decentralized exchange in crypto. Live from the first day of Sui mainnet, Cetus is the leading DEX and aggregator on Sui, serving as the key liquidity and swap infra of the Sui ecosystem. The mission of Cetus is building a powerful and flexible underlying liquidity network to make trading easier for any users and assets.

Scope

In scope
TargetTypeSeverity

!! Only smart contracts residing in the sources folder and dependencies are in scope. The rest is there to make testing easier !! The program scope contains both our CLMM and DLMM services.

Please contact HackenProof support team in Discord to get access to the full scope. KYC required.

Smart ContractCritical
Smart ContractCritical

Focus Area

  • Critical bounty: up to 10% of the total funds at risk, capped at $1,000,000. Critical rewards are calculated based on the total funds at risk from the specific vulnerability, subject to the maximum bounty cap. The applicable funds-at-risk amount will be determined by the demonstrated impact scope of the vulnerability and may include a single pool, multiple pools, or broader protocol funds where applicable.
  • A finding is considered Critical only if it is directly exploitable, does not depend on additional conditions, and can lead to direct loss of user funds

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
  • Bug in dependencies that does materially compromise an in-scope Cetus contract

OUT OF SCOPE VULNERABILITIES: Smart Contracts

  • Theoretical vulnerabilities without any proof or demonstration
  • Old compiler version
  • The compiler version is not locked
  • Vulnerabilities in dependencies that have no demonstrated impact on Cetus
  • 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

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

All reports, findings, supporting materials, and related information submitted under this program must remain confidential, regardless of whether the report is accepted, rejected, duplicated, out of scope, or otherwise ineligible for a reward.

For accepted findings, confidentiality must continue for at least 180 days after the issue has been fully resolved in production.

Any public disclosure relating to a submitted report requires prior notice to Cetus and Cetus’s written consent. Researchers may request disclosure after the applicable confidentiality period, and any approved disclosure must be coordinated with the team regarding timing, scope, and technical details.

Response Type (SLA)

  • First response: 72 hours
  • Triage time: 72 hours
  • Reward time: 3 business days
  • Resolution time: 14 business days