Shiba Memu - Audit

CertiK5 Jul 2023Files named in the report

CertiK reviewed Shiba Memu (Shiba Memu - Audit) on 5 Jul 2023: 7 findings, 0 critical; 3 marked fixed, 2 acknowledged, 2 open.

No open critical findings

Open the report Open Shiba Memu’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings7

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	2	0	0
Medium	0	0	2
Low	0	2	1

HighCentralization Related RisksOpen

In the contract `SHMUPresale` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the owner account may allow a hacker to take advantage of this authority and pause/unpause the contract, change the owner, set presale amount, add/remove user from blacklist, claim unsold tokens, receive presale profits. ![](https://accelerator-tasks-staging.acc.corp.certik.com/cb9dcbbd7de54a76b44d5ca27adfc17d/diagrams/centralization_SHMUPresale-SHMUPresale-_owner.svg)

HighInitial Token DistributionOpen

All of the SHMU tokens are sent to the contract deployer. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.