Router Integration audit
Oak Security reviewed Router Protocol (Router Integration audit) on 29 May 2024: 5 findings, 1 critical; 4 marked fixed, 1 acknowledged.
1 critical finding, fixed
Open the reportOpen Router Protocol’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 | 1 |
| High | 0 | 0 | 3 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 1 | 0 |
CriticalFailed cross-chain requests are repeatedly processed in Router Chain’s EndBlocker, potentially causing Denial-of-ServiceFixed
The report gives no description here.
HighFee settlement can be bypassed for inbound and crosstalk requests, resulting in relayers not being compensatedFixed
The report gives no description here.
HighMalicious relayer can purposefully fail cross-chain requests on EVM destination chainsFixed
The report gives no description here.
HighNEAR gateway contract does not allocate sufficient gas for handler callsFixed
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 Router Protocol’s security record
Router ProtocolAudits2 audits by 1 firmLast audit May 2024, by Oak Security.
Critical findingsNo open critical findingsAcross the 2 reports, 8 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Router Protocol’s security recordSecurity firm
Oak Security33 projects reviewed · 60 reports · latest May 2026
See Oak Security’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