Injective security record
As of 21 Oct 2026, Injective has 3 audit reports by 2 security firms on Trustblock; the latest is by HashEx, dated 6 Aug 2024. Those reports list no open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits3
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Injective | Security firm: HashEx | Date: | Scope: 1 address on Ethereum | No open critical findings | Open · hashex.org |
| Ninja audit | Security firm: Oak Security | Date: | Scope: Not recorded (see the report) | 1 critical finding, fixed | Open · GitHub |
| Injective audit | Security firm: Oak Security | Date: | Scope: Not recorded (see the report) | 1 critical finding, fixed | Open · GitHub |
Findings23
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 2 |
| High | 0 | 3 | 2 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 3 | 13 |
Marked Informational by the firms. Not counted as findings.
InformationalContracts should implement a two step ownership transferNinja audit · Oak Security · 20 Jan 2023Acknowledged
The report gives no description here.
Open the reportInformationalCustom access control implementationNinja audit · Oak Security · 20 Jan 2023Acknowledged
The report gives no description here.
Open the reportInformationalName validation can be bypassed with whitespaceInjective audit · Oak Security · 20 Jan 2023Acknowledged
The report gives no description here.
Open the reportInformationalOverflow checks not enabled for release profileNinja audit · Oak Security · 20 Jan 2023Acknowledged
The report gives no description here.
Open the reportInformationalRedundant validation of variablesNinja audit · Oak Security · 20 Jan 2023Acknowledged
The report gives no description here.
Open the reportInformationalA dev-dependency is vulnerable to two CVEsInjective audit · Oak Security · 20 Jan 2023Fixed
The report gives no description here.
Open the reportInformationalConsider deduping batch contract addresses in ValidateBasicInjective audit · Oak Security · 20 Jan 2023Fixed
The report gives no description here.
Open the reportInformationalOutstanding TODO and FIXME comments present in the codebaseNinja audit · Oak Security · 20 Jan 2023Fixed
The report gives no description here.
Open the reportInformationalOutstanding TODO comments present in the codebaseInjective audit · Oak Security · 20 Jan 2023Fixed
The report gives no description here.
Open the reportInformationalUse of magic numbersNinja audit · Oak Security · 20 Jan 2023Fixed
The report gives no description here.
Open the reportContracts1
| Address | Chain | Source code |
|---|---|---|
| 0xe28b3b32b6c345a34ff64674606124dd5aceca30 | Chain: Ethereum | Source code: Verified source |
Show this on your site
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Content
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="injective"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
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.
Tell us