OnRe - mmbot

QuantstampCode version: not recorded (see the report)

Quantstamp reviewed OnRe (OnRe - mmbot) on 7 Apr 2026: 1 finding, 0 critical; it is marked fixed.

No open critical findings
Open the reportOpen OnRe’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings3

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low001

Marked Informational by the firm. Not counted as findings.

InformationalInitialization Accepts Caller-Supplied Program ReferenceAcknowledged

The initialize instruction accepts `onre_program_id` as a caller-supplied parameter. This value is used to validate the `onre_state` account via owner and seeds constraints, and is then stored permanently in `ProgramState`. All subsequent boss and admin authorization checks (`withdraw`, `set_executor`, `set_kill_switch`) derive the `onre_state` PDA from this stored value. However, because `onre_program_id` is a free parameter at initialization, an attacker who observes the program deployment can front-run the legitimate initialization by deploying their own fake program with a state PDA containing the attacker's pubkey as boss. The attacker calls initialize with their fake `onre_program_id`, signs as the boss that matches their fake state, and all Anchor validations pass. The `ProgramState` is then permanently linked to the attacker's program. Since init can only be called once, the legitimate team is locked out. This could lead to full program takeover if initialization is not performed atomically with deployment. The attacker would control the boss role, could set the executor to their own key, disable the kill switch, and withdraw any funds deposited after the hijack. The legitimate boss of the real Onre program would have no authority over the mmbot program.

Informational`swap_orca` Does Not Allow Inclusion of Supplementary Tick Arrays, Meaning Valid Swaps May Sometimes FailFixed

The `swap_v2` implementation allows any `remaining_accounts_info` passed in the data to be included as supplementary tick arrays on top of the three default tick arrays provided. Requiring that the swap is executed within the three default tick arrays may mean some swaps that can be executed correctly may unexpectedly fail. The likelihood of this increases if the liquidity across ticks is shallow or if the size of the desired swap is large.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of OnRe’s security record

OnRe
Audits6 audits by 1 firmLast audit Sep 2026, by Quantstamp.
Critical findingsNo open critical findingsAcross 6 reports.
Open OnRe’s security record

Security firm

Quantstamp

240 projects reviewed · 338 reports · latest Nov 2026

See Quantstamp’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us