Hegic audit reports

Arbitrum, Ethereum, Fantomhegic.coXGitHub

Hegic has 4 public audit reports from PeckShield; the latest is PeckShield, 18 Oct 2022; 1 critical finding, marked fixed by the firm. It also holds 1 incident (latest 23 Apr 2020).

Critical findings
No open critical findings
Across the 4 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it. See the findings
Incident
Incident 23 Apr 2020
Source: De.Fi incident database. 4 audits have been published since. See the incident
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 firm3

Statuses are the security firms’ own

3 findings are still open or acknowledged in the firms’ reports: 2 medium, 1 low (1 open, 2 acknowledged).

Medium
2
Low
1
  • Medium Acknowledged

    Trust Issue of Admin Keys

    Hegic Herge Protocol Upgrade audit · PeckShield · 18 Oct 2022 · Report ↗

  • Medium Acknowledged

    Trust Issue of Admin Keys

    Hegic HardCore Beta audit · PeckShield · 26 Feb 2022 · Report ↗

  • Low Open

    Possible Front-Running Against Pool Withdrawals And Staking

    Hegic audit · PeckShield · 1 Oct 2020 · Report ↗

Incidents1

Attached through a shared contract address. Our incident data ends in Nov 2026.

Incident

Incident,

' This resulted in no liquidity for expiring contracts since user assets were locked whenever they did not utilize their options.

Source: De.Fi incident database.

Audits before it
0.
Audits since
4, the latest dated 18 Oct 2022.

Audits4

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Hegic Herge Protocol Upgrade auditSecurity firm: PeckShieldDate: Scope: Not recorded; see the reportNone openFindings: 2 high · 1 medium · 1 low
3 fixed · 1 acknowledged
GitHub ↗
Hegic HardCore Beta auditSecurity firm: PeckShieldDate: Scope: Not recorded; see the reportNone openFindings: 1 high · 2 medium · 5 low
7 fixed · 1 acknowledged
GitHub ↗
Hegic auditSecurity firm: PeckShieldDate: Scope: Not recorded; see the reportNone openFindings: 1 high · 1 medium · 4 low
5 fixed
GitHub ↗
Hegic auditSecurity firm: PeckShieldDate: Scope: Not recorded; see the report1 critical finding, fixedFindings: 1 critical · 4 medium · 2 low
6 fixed · 1 open
GitHub ↗

Findings27

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

SeverityOpenAcknowledgedFixed
Critical001
High003
Medium025
Low107
LowPossible Front-Running Against Pool Withdrawals And StakingHegic audit · PeckShield · 1 Oct 2020Open

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

Hegic: questions

Is Hegic audited?

Trustblock holds 4 public audit reports for Hegic, dated 1 Oct 2020 to 18 Oct 2022. The latest is by PeckShield (“Hegic Herge Protocol Upgrade audit”).

Who audited Hegic?

PeckShield wrote the 4 reports Trustblock holds for Hegic.

Are there open findings in Hegic’s audits?

3 findings are still open or acknowledged in the firms’ reports: 2 medium, 1 low (1 open, 2 acknowledged). Of 1 critical finding: marked fixed by the firm. 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="hegic"
></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