Injective audit reports

Injective has 3 public audit reports from Oak Security and HashEx; the latest is HashEx, 6 Aug 2024; 2 critical findings, all marked fixed by the firms. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
Across the 3 reports, 2 critical findings were reported. Each is marked fixed by the firm that reported it. See the findings
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm6

Statuses are the security firms’ own

6 findings are still open or acknowledged in the firms’ reports: 3 high, 3 low (all acknowledged).

High
3
Low
3
  • High Acknowledged

    Inventory imbalance under certain parameter constellations will disable the risk management framework

    Ninja audit · Oak Security · 20 Jan 2023 · Report ↗

  • High Acknowledged

    Price threshold for price invalidity is prone to manipulation and might lead to full loss of users funds in case of a breakdown of a market or an asset

    Ninja audit · Oak Security · 20 Jan 2023 · Report ↗

  • High Acknowledged

    registry contract and wasmx module are not aware of registered contract migrations

    Injective audit · Oak Security · 20 Jan 2023 · Report ↗

  • Low Acknowledged

    Backward looking volatility can lead to inefficient pricing

    Ninja audit · Oak Security · 20 Jan 2023 · Report ↗

  • Low Acknowledged

    Math utils do not follow best practices

    Ninja audit · Oak Security · 20 Jan 2023 · Report ↗

  • Low Acknowledged

    Vault contract invocations should be prevented prior to registration with master contract

    Ninja audit · Oak Security · 20 Jan 2023 · Report ↗

Audits3

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
InjectiveSecurity firm: HashExDate: Scope: 1 address on EthereumNone openFindings: None listedhashex.org ↗
Ninja auditSecurity firm: Oak SecurityDate: Scope: Not recorded; see the report1 critical finding, fixedFindings: 1 critical · 2 high · 12 low
10 fixed · 5 acknowledged
GitHub ↗
Injective auditSecurity firm: Oak SecurityDate: Scope: Not recorded; see the report1 critical finding, fixedFindings: 1 critical · 3 high · 4 low
7 fixed · 1 acknowledged
GitHub ↗

Findings33

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical002
High032
Medium000
Low0313

No open finding in these reports.

Contracts1

AddressChainSource code
0xe28b3b32b6c345a34ff64674606124dd5aceca30Chain: EthereumSource code: Verified source

Injective: questions

Is Injective audited?

Trustblock holds 3 public audit reports for Injective, dated 20 Jan 2023 to 6 Aug 2024. The latest is by HashEx (“Injective”).

Who audited Injective?

2 security firms wrote the reports Trustblock holds for Injective: Oak Security and HashEx.

Are there open findings in Injective’s audits?

6 findings are still open or acknowledged in the firms’ reports: 3 high, 3 low (all acknowledged). Of 2 critical findings: all marked fixed by the firms. Statuses are the security firms’ own.

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

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-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