DSToken

Halborn25 Sep 2025Code version: not recorded (see the report)

Halborn reviewed Securitize (DSToken) on 25 Sep 2025: 6 findings, 0 critical; 4 marked fixed, 2 acknowledged.

No open critical findings

Open the report Open Securitize’s security record

Report hosted on halborn.com.

Trustblock does not review code.

Findings6

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	2
Low	0	2	2

Marked Informational by the firm. Not counted as findings.

InformationalMissing Two-Step Ownership Transfer Protection in ServiceConsumerAcknowledged

The report gives no description here.

InformationalPotential Out-of-Gas Risk in getTokenBalances for Large Input ArraysAcknowledged

The report gives no description here.

InformationalUnnecessary dynamic array allocation in issueTokensCustom wastes gasAcknowledged

The report gives no description here.

InformationalIncorrect Loop Variable Type in _registerNewInvestorFixed

The report gives no description here.

InformationalIncorrect Maximum Holdings Check Prevents Valid TransfersFixed

The report gives no description here.

InformationalInefficient use of dynamic array for fixed-length parametersFixed

The report gives no description here.

InformationalMissing input validation in issueTokensWithNoCompliance functionFixed

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

Halborn

17 projects reviewed · 44 reports · latest Jul 2026

See Halborn’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.