Derive security review

Sigma PrimeCode version: not recorded (see the report)

Audit · firm’s term: security review

Sigma Prime reviewed Derive (Derive security review) on 1 Sep 2024: 16 findings, 4 critical; 11 marked fixed, 5 acknowledged.

4 critical findings, fixed
Open the reportOpen Derive’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings16

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

SeverityOpenAcknowledgedFixed
Critical004
High002
Medium022
Low033

Marked Informational by the firm. Not counted as findings.

InformationalExpired Options can be CreatedAcknowledged

The report gives no description here.

InformationalFee-On-Transfer Tokens Are Not SupportedAcknowledged

The report gives no description here.

InformationalMaximum Values can be Set Below Current ValuesAcknowledged

The report gives no description here.

InformationalMiscellaneous General CommentsAcknowledged

The report gives no description here.

InformationalOracles Using Perp Market Prices Can Be ManipulatedAcknowledged

The report gives no description here.

InformationalTrading with Self to Make a Loss is ProfitableAcknowledged

The report gives no description here.

InformationalForceWithdraw Can Cause USDC To Become StuckFixed

The report gives no description here.

InformationalHigh Reentrancy Potential in subAccounts.submitTransfers()Fixed

The report gives no description here.

InformationalIncorrect EmitsFixed

The report gives no description here.

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 Derive’s security record

Derive
Audits6 audits by 2 firmsLast audit Mar 2025, by Sigma Prime.
Critical findings1 critical acknowledged, not fixedReported in “Derive security review” by Sigma Prime, Jan 2025. The team acknowledged it.
Open Derive’s security record

Security firm

Sigma Prime

16 projects reviewed · 37 reports · latest Aug 2026

See Sigma Prime’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