Monkecoin

CertiK1 address on BNB Chain

CertiK reviewed Monke (Monkecoin) on 29 Mar 2024: 14 findings, 0 critical; 3 marked fixed, 11 open.

No open critical findings
Open Monke’s security record

The original report was removed from its address (seen 19 Oct 2026).

Trustblock does not review code.

Findings14

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

SeverityOpenAcknowledgedFixed
Critical000
High101
Medium300
Low702
HighInitial Token DistributionOpen

All of the `Monkecoin` tokens are sent to the contract deployer. This is a centralization risk because the deployer 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.

MediumOld Router Retains Infinite AllowanceOpen

There exists functionality to update the `dexRouter` used. However, upon update, the new `dexRouter` is given infinite allowance, and the account corresponding to the old `dexRouter` also retains infinite allowance.

MediumPotential significant impact on the token price iOpen

The contract contains a function `enableTrading()` which initializes the `swapAmount` without a maximum value constraint. This lack of validation can lead to the `swapAmount` being set to an excessively high number. In the `_transfer()` function, when a sell action is performed, `Monkecoin` fees collected in the contract are swapped for BNB if `contractSwapEnabled` is true and the `swapThreshold` is met. The absence of a maximum `swapAmount` check in the `enableTrading()` function creates a vulnerability where a large `swapAmount` could be executed, potentially resulting in a significant amount of `Monkecoin` being sold on the DEX pair, leading to a drastic price drop.

MediumThird-Party Dependency UsageOpen

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=136 IRouter02 public dexRouter; ``` - The contract `Monkecoin` interacts with third party contract with `IRouter02` interface via `dexRouter`. --- ```solidity=150 Initializer initializer; ``` - The `Initializer` is an unverified contract. The contract `Monkecoin` interacts with the `Initializer` contract: - The `initializer.checkUser()` function is called in token transfer process to perform token transfer checks and block blacklisted users. - The token contract is initiated with configurations provided by the `Initializer`, e.g. LP pair address, DEX router addresses, `swapThreshold` and `swapAmount`.

LowComment InconsistencyOpen

```solidity=187 function transferOwner(address newOwner) external onlyOwner { require(newOwner != address(0), "Call renounceOwnership to transfer owner to the zero address."); require(newOwner != DEAD, "Call renounceOwnership to transfer owner to the zero address."); ``` The function name mentioned in the error messages should be `transferOwner`. Line 189 checks that `newOwner` is not the DEAD address, but the message advises to check for "the zero address". --- ```solidity=381 require(swapAmount >= _tTotal / 1_000_000, "Cannot be lower than 0.00001% of total supply."); require(swapThreshold >= _tTotal / 1_000_000, "Cannot be lower than 0.00001% of total supply."); ``` The "0.00001% of total supply" should be `_tTotal / 10_000_000`. --- ```solidity=531 require(token != address(this), "Cannot sweep native tokens."); ``` The token checked is `Monkecoin`.

LowInefficient Check for Presale Addresses in TokenOpen

The token selling process includes a check (L456) to verify whether the token transfer destination address is a presale address. The token selling process involves transferring tokens to a DEX pair (L439). The function then proceeds to verify whether the transfer destination address is a presale address (L456). This verification appears unnecessary since, by design, a DEX pair cannot be considered a presale address.

LowNo Slippage CheckOpen

A sandwich attack may happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (executing before the target) a transaction to purchase one of the assets and make profits by backrunning (executing after the target) a transaction to sell the asset.

LowThe `maxBuyTaxes` is constantly zeroOpen

The `maxBuyTaxes` consistently remains at zero: ```solidity=130 uint256 constant public maxBuyTaxes = 0; ``` Consequently, the `buyFee` is always zero, rendering the `buyFee` redundant as it never comes into effect.

LowThe new owner is not added to `_liquidityHolders`Open

In the `constructor()`, the owner is added to the `_liquidityHolders`. However, in the function `transferOwner()`, the new owner is not added to the `_liquidityHolders` and the old owner is not removed from the `_liquidityHolders`. The old owner still has the issue in the function `renounceOwnership()`.

LowUnreasonable ApprovalOpen

The allowance should be approved to the router based on the token swapping amount in the `contractSwap()` function. Therefore, approving the maximum allowance to the router could be unsecure as the DEX router may be compromised. The owner approves maximum allowance to the router, which is unnecessary. Additionally, the approval is not revoked when the owner's role is transferred or renounced.

Show 1 more
LowUsage of `transfer`/`send` for Sending Native TokOpen

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring native tokens, since some contracts may not be able to receive the funds. Those functions forward only a fixed amount of gas (2300 specifically) and the receiving contracts may run out of gas before finishing the transfer. Also, EVM instructions' gas costs may increase in the future. Thus, some contracts that can receive now may stop working in the future due to the gas limitation. ```solidity=526 payable(_owner).transfer(address(this).balance); ``` - `Monkecoin.sweepContingency` uses `transfer()`.

Contracts in scope1

AddressChainSource code
0xfce692762e907e80a061c01631d15ba7328eaaaaChain: BNB ChainSource code: Verified source

Part of Monke’s security record

Monke
Audits2 audits by 2 firmsLast audit Mar 2024, by CertiK.
Critical findingsNo open critical findingsAcross 2 reports.
Open Monke’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 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