Injective audit
Oak Security reviewed Injective (Injective audit) on 20 Jan 2023: 8 findings, 1 critical; 7 marked fixed, 1 acknowledged.
1 critical finding, fixed
Open the reportOpen Injective’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings8
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 1 | 2 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 4 |
Marked Informational by the firm. Not counted as findings.
InformationalName validation can be bypassed with whitespaceAcknowledged
The report gives no description here.
InformationalA dev-dependency is vulnerable to two CVEsFixed
The report gives no description here.
InformationalConsider deduping batch contract addresses in ValidateBasicFixed
The report gives no description here.
InformationalOutstanding TODO comments present in the codebaseFixed
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 Injective’s security record
InjectiveAudits3 audits by 2 firmsLast audit Aug 2024, by HashEx.
Critical findingsNo open critical findingsAcross the 3 reports, 2 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Injective’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