Harambe AI Token

CertiK1 address on Ethereum

CertiK reviewed Harambe AI Token on 5 Feb 2024: 5 findings, 0 critical; 2 acknowledged, 3 open.

No open critical findings
Open the reportOpen Harambe AI Token’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings5

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

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium010
Low300
LowFunction Misses Zero Address ValidationOpen

It is expected that calls of the form `approve(spender, amount)` fail if the address in `spender` is the zero address. It is expected that calls of the form `transferFrom(from, dest, amount)` fail for transfers from or to the zero address. However, the `transferFrom` function in `HARAMBEToken` can transfer tokens from or to the zero address. It is expected that calls of the form `transfer(recipient, amount)` fail if the recipient address is the zero address.

LowUser-Defined GettersOpen

The linked functions are equivalent to the compiler-generated getter functions for the respective variables.

LowVariables That Could Be Declared as ImmutableOpen

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

Contracts in scope1

AddressChainSource code
0x5484581038cbf8ef33b7f6daec7a2f01f71db3c2Chain: EthereumSource code: Verified source

Part of Harambe AI Token’s security record

Harambe AI Token
Audits1 audit by 1 firmLast audit Feb 2024, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Harambe AI Token’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