Ninja audit

Oak Security20 Jan 2023Code version: not recorded (see the report)

Audit · firm’s term: security audit

Oak Security reviewed Injective (Ninja audit) on 20 Jan 2023: 15 findings, 1 critical; 10 marked fixed, 5 acknowledged.

1 critical finding, fixed

Open the report Open Injective’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings15

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	1
High	0	2	0
Medium	0	0	0
Low	0	3	9

HighInventory imbalance under certain parameter constellations will disable the risk management frameworkAcknowledged

The report gives no description here.

HighPrice 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 assetAcknowledged

The report gives no description here.

LowBackward looking volatility can lead to inefficient pricingAcknowledged

The report gives no description here.

LowMath utils do not follow best practicesAcknowledged

The report gives no description here.

LowVault contract invocations should be prevented prior to registration with master contractAcknowledged

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

Injective

Audits3 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 record

Security firm

Oak Security

33 projects reviewed · 60 reports · latest May 2026

See Oak Security’s audits

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.