Securitize DSToken Rebasing Audit Report

CyfrinCode version: not recorded (see the report)

Cyfrin reviewed Securitize (Securitize DSToken Rebasing Audit Report) on 10 Oct 2025: 33 findings, 1 critical; 23 marked fixed, 10 acknowledged.

1 critical finding, fixed
Open the reportOpen Securitize’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings33

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

SeverityOpenAcknowledgedFixed
Critical001
High000
Medium045
Low0617
MediumComplianceServiceRegulated applies double locking to investor transferable tokens leading to DoS of transfersAcknowledged

The report gives no description here.

MediumeuRetailInvestorsCount is susceptible to underflow when transferring tokens between retail and qualified investors of the same country on the EU regionAcknowledged

The report gives no description here.

MediumHistorical token issuances become subject to new lock-up requirements when users change residencyAcknowledged

The report gives no description here.

MediumToken value locks done as part of issuance restrict subsequently transferred unlocked tokens after negative rebasingAcknowledged

The report gives no description here.

LowAttribute changes via setAttribute or updateInvestor do NOT trigger compliance count updates.Acknowledged

The report gives no description here.

LowNo way for users to invalidate nonce used to signAcknowledged

The report gives no description here.

LowNot maximum amount of issuances enforceAcknowledged

The report gives no description here.

LowProtocol will leak value to users due to rounding in RebasingLibraryAcknowledged

The report gives no description here.

LowSeized tokens will be stuck on the receiver of the seized funds because it is not an investor and never receives investorsBalanceAcknowledged

The report gives no description here.

LowStale Issuance Records After Burn and Seize OperationsAcknowledged

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

Securitize
Audits37 audits by 2 firmsLast audit Sep 2026, by Cyfrin.
Critical findingsNo open critical findingsAcross the 37 reports, 6 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Securitize’s security record

Security firm

Cyfrin

28 projects reviewed · 79 reports · latest Sep 2026

See Cyfrin’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