Hector Network (Redemption System) Audit
CertiK reviewed Hector Network (Hector Network (Redemption System) Audit) on 19 Dec 2023: 8 findings, 0 critical; 2 marked fixed, 6 open.
The original report was removed from its address (seen 18 Oct 2026).
Trustblock does not review code.
Findings8
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 1 | 0 | 0 |
| Low | 4 | 0 | 1 |
HighLack of Access Control Could Lead to Fund LossFixed
The `mintWithdraw()` function doesn't have any access control and it can be called by anyone. An attacker can call the function with itself as the `recipient` and an arbitrary `redeemAmount`, thus draining the funds from the Redemption Treasury contract.
LowUnused Return ValueFixed
The smart contract does not check or store the return value of an external call in a local or state variable, which may introduce vulnerabilities due to the unhandled outcome.
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.
Repository and files the report names (7)
- liquidation/contracts/redemption/HectorRedemptionTreasury.sol
- liquidation/contracts/redemption/LockAccessControl.sol
- liquidation/contracts/redemption/TokenVault.sol
- liquidation/contracts/redemption/FNFT.sol
- liquidation/contracts/redemption/HectorRedemption.sol
- liquidation/contracts/redemption/LockAddressRegistry.sol
- liquidation/contracts/registration/HectorRegistration.sol
Part of Hector Network’s security record
Security firm
CertiK1,044 projects reviewed · 1,375 reports · latest May 2025
See CertiK’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