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
HighInitial Token DistributionAcknowledged

All of the `Harambe AI Token` tokens are sent to the hard-coded address `0x06D344b9ada316c83C30110Ca6029d49961eC907`. This is a centralization risk because this account can distribute tokens without obtaining the consensus of the community. Any compromise to this account may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

MediumFunction Calls User-Provided Addresses With No AcAcknowledged

Calling a user provided address is dangerous, especially in a public function with no access control restriction. An attacker could deploy a malicious contract and use the vulnerable function to trigger a call to the malicious contract, potentially stealing user funds or causing other serious damages. In this contract, if an approver mistakenly approves a malicious spender by calling the `approveAndCall` function, the spender can immediately callback to this contract and spend the entire approved allowance within the same transaction, leaving no chance for the approver to revoke the allowance. We would like to discuss this finding with the team to ensure that the design is intentional.

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