Securitize DSToken Compliance Diff Audit Report
Cyfrin reviewed Securitize (Securitize DSToken Compliance Diff Audit Report) on 4 Jun 2026: 5 findings, 0 critical; 4 marked fixed, 1 acknowledged.
No open critical findings
Open the reportOpen Securitize’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings5
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 3 |
| Low | 0 | 1 | 1 |
MediumComplianceServicePermissionless::_lockedAt and ComplianceServicePermissionless::_cleanupIssuances perform unguarded timestamp + lockPeriod addition, allowing a transfer agent to freeze transfers and iFixed
The report gives no description here.
MediumComplianceServicePermissionless::recordIssuance writes a lockup record even when the lock period is zero, causing tokens minted with no lockup to be retroactively locked when a lockup is later enabledFixed
The report gives no description here.
MediumTokenLibrary::issueTokensCustom routes every manual lock under permissionless into a single shared investorsLocks[""] bucket, exhausting the global 30-lock cap and DoS-ing all future issuances with maFixed
The report gives no description here.
LowWalletManager::setSpecialWallet guard is inert under the stub registry, letting an Issuer label any token-holding wallet as a platform wallet and bypass an active lockupFixed
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
SecuritizeAudits37 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 recordSecurity firm
Cyfrin28 projects reviewed · 79 reports · latest Sep 2026
See Cyfrin’s auditsSomething 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