DeXe / DEX
Hacken reviewed DeXe Protocol (DeXe / DEX) on 19 Jun 2023: 33 findings, 2 critical; 15 marked fixed, 18 open.
Report hosted on hacken.io.
Trustblock does not review code.
Findings33
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 2 | 0 | 0 |
| High | 7 | 0 | 7 |
| Medium | 2 | 0 | 5 |
| Low | 7 | 0 | 3 |
CriticalFlashloan Attack; Front-Running AttackOpen
The report gives no description here.
CriticalUnverified InteractionOpen
The report gives no description here.
HighAccess Control Violation; Race ConditionsOpen
The report gives no description here.
HighAssets Integrity; Undocumented BehaviorOpen
The report gives no description here.
HighDenial of Service VulnerabilityOpen
The report gives no description here.
HighDenial of Service VulnerabilityOpen
The report gives no description here.
HighRequirements ViolationOpen
The report gives no description here.
HighRequirements ViolationOpen
The report gives no description here.
HighRequirements Violation; Misleading NamingOpen
The report gives no description here.
MediumContradiction - Invalid Return ActionOpen
The report gives no description here.
Show 8 more
MediumInconsistent Data - Unused Return ValueOpen
The report gives no description here.
LowFloating PragmaOpen
The report gives no description here.
LowFunction Which May Be Declared PrivateOpen
The report gives no description here.
LowMissing EventsOpen
The report gives no description here.
LowMissing Zero Address ValidationOpen
The report gives no description here.
LowRedundant ImportOpen
The report gives no description here.
LowShadowing State VariablesOpen
The report gives no description here.
LowUnindexed EventsOpen
The report gives no description here.
Contracts in scope1
| Address | Chain |
|---|---|
| 0xde4ee8057785a7e8e800db58f9784845a5c2cbd6 | Chain: Ethereum |
Part of DeXe Protocol’s security record
DeXe ProtocolSecurity firm
Hacken343 projects reviewed · 476 reports · latest Sep 2026
See Hacken’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