Hugo Inu - Audit

CertiK1 address on BNB Chain

Audit

CertiK reviewed Hugo Inu (Hugo Inu - Audit) on 16 Jun 2023: 14 findings, 0 critical; 1 marked fixed, 2 acknowledged, 11 open.

No open critical findings
Open the reportOpen Hugo Inu’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings14

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

SeverityOpenAcknowledgedFixed
Critical000
High011
Medium010
Low1100
HighInitial Token DistributionAcknowledged

All `HUGO` tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute `HUGO` tokens without the consensus of the community.

MediumVariable `_rOwned[account]` Not Updated in FunctiAcknowledged

Variable `_rOwned[account]` is not updated in the function `includeInReward()`, which will make the accounts included siphon off the tokens out of the balances of all token holders. The Rate was higher at the moment of the `excludeFromReward(account)` call, so the `_rOwned[account] / _tOwned[account]` ratio is bigger than expected for accounts included in the reward. As of 06/08/2023, the ownership has been renounced in the transaction [0x54cdd0625d2d9f2bf12757b882daeabafbe996bab437d293bac86d36fe5459d1](https://bscscan.com/tx/0x54cdd0625d2d9f2bf12757b882daeabafbe996bab437d293bac86d36fe5459d1). The `includeInReward()` function is no longer executable, but the issue is still present in the code.

Contracts in scope1

AddressChainSource code
Chain: BNB ChainSource code: Verified source

Part of Hugo Inu’s security record

Hugo Inu
Audits1 audit by 1 firmLast audit Jun 2023, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Hugo Inu’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 reports · latest May 2025

See CertiK’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.

Tell us