Monke audit reports

Monke has 2 public audit reports from CertiK and Cyberscope; the latest is CertiK, 29 Mar 2024; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
Across 2 reports.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm17

Statuses are the security firms’ own

17 findings are still open or acknowledged in the firms’ reports: 1 high, 3 medium, 13 low (all open).

High
1
Medium
3
Low
13
  • High Open

    Initial Token Distribution

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Medium Open

    Old Router Retains Infinite Allowance

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Medium Open

    Potential significant impact on the token price i

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Medium Open

    Third-Party Dependency Usage

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Low Open

    Comment Inconsistency

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Low Open

    Inefficient Check for Presale Addresses in Token

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Low Open

    No Slippage Check

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Low Open

    The `maxBuyTaxes` is constantly zero

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Low Open

    The new owner is not added to `_liquidityHolders`

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

  • Low Open

    Unreasonable Approval

    Monkecoin · CertiK · 29 Mar 2024 · Report ↗

All 17 open and acknowledged findings

Audits2

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
MonkecoinSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 2 high · 3 medium · 9 low
3 fixed · 11 open
Original removed
MonkecoinSecurity firm: CyberscopeDate: Scope: 1 address on BNB ChainNone openFindings: 6 low
6 open
cyberscope.io ↗

Findings20

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

SeverityOpenAcknowledgedFixed
Critical000
High101
Medium300
Low1302
HighInitial Token DistributionMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
MediumOld Router Retains Infinite AllowanceMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
MediumPotential significant impact on the token price iMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
MediumThird-Party Dependency UsageMonkecoin · CertiK · 29 Mar 2024Open

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`.

Open the report
LowComment InconsistencyMonkecoin · CertiK · 29 Mar 2024Open

```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`.

Open the report
LowInefficient Check for Presale Addresses in TokenMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
LowNo Slippage CheckMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
LowThe `maxBuyTaxes` is constantly zeroMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
LowThe new owner is not added to `_liquidityHolders`Monkecoin · CertiK · 29 Mar 2024Open

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()`.

Open the report
LowUnreasonable ApprovalMonkecoin · CertiK · 29 Mar 2024Open

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.

Open the report
Show 7 more
LowUsage of `transfer`/`send` for Sending Native TokMonkecoin · CertiK · 29 Mar 2024Open

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()`.

Open the report
LowUntitled findingMonkecoin · Cyberscope · 9 Mar 2024Open

The report gives no description here.

Open the report
LowUntitled findingMonkecoin · Cyberscope · 9 Mar 2024Open

The report gives no description here.

Open the report
LowUntitled findingMonkecoin · Cyberscope · 9 Mar 2024Open

The report gives no description here.

Open the report
LowUntitled findingMonkecoin · Cyberscope · 9 Mar 2024Open

The report gives no description here.

Open the report
LowUntitled findingMonkecoin · Cyberscope · 9 Mar 2024Open

The report gives no description here.

Open the report
LowUntitled findingMonkecoin · Cyberscope · 9 Mar 2024Open

The report gives no description here.

Open the report

Contracts1

AddressChainSource code
0xfce692762e907e80a061c01631d15ba7328eaaaaChain: BNB ChainSource code: Verified source

Monke: questions

Is Monke audited?

Trustblock holds 2 public audit reports for Monke, dated 9 Mar 2024 to 29 Mar 2024. The latest is by CertiK (“Monkecoin”).

Who audited Monke?

2 security firms wrote the reports Trustblock holds for Monke: CertiK and Cyberscope.

Are there open findings in Monke’s audits?

17 findings are still open or acknowledged in the firms’ reports: 1 high, 3 medium, 13 low (all open). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="monkecoin"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

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