Biceps Coin audit reports

Biceps Coin has 1 public audit report from CertiK; dated 19 Apr 2024; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
In 1 report.
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 firm12

Statuses are the security firms’ own

12 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 9 low (9 open, 3 acknowledged).

High
1
Medium
2
Low
9
  • High Acknowledged

    Initial Token Distribution

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Medium Acknowledged

    Contract gains non-withdrawable BNB via the `_swa

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Medium Acknowledged

    Potential Out-of-Gas Exception

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Init Functions Are Susceptible To Front-running

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Missing Emit Events

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Missing Error Messages

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Missing Zero Address Validation

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Potential Sandwich Attacks

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Redundant False

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

  • Low Open

    Third-Party Dependency Usage

    Biceps - audit · CertiK · 19 Apr 2024 · Report ↗

All 12 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Biceps - auditSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 2 high · 2 medium · 9 low
1 fixed · 3 acknowledged · 9 open
skynet.certik.com ↗

Findings13

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

SeverityOpenAcknowledgedFixed
Critical000
High011
Medium020
Low900
LowInit Functions Are Susceptible To Front-runningBiceps - audit · CertiK · 19 Apr 2024Open

The `initialize()` functions below are not called by another contract atomically after the contract is deployed, so it's possible for a malicious user to call `initialize()` which, if it's noticed in time, would require the project to re-deploy the contract in order to properly initialize. ----- Onchain Data The team successfully executed the deployment of this contract and its initialization within a single transaction: [0x7a3364a511fb1b25902bb78c4b9ca4bed9b9c336dd133dabc0fcc3e2fcb8cdfa](https://bscscan.com/tx/0x7a3364a511fb1b25902bb78c4b9ca4bed9b9c336dd133dabc0fcc3e2fcb8cdfa). However, should the contract be deployed anew, the same problem will persist.

Open the report
LowMissing Emit EventsBiceps - audit · CertiK · 19 Apr 2024Open

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

Open the report
LowMissing Error MessagesBiceps - audit · CertiK · 19 Apr 2024Open

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

Open the report
LowMissing Zero Address ValidationBiceps - audit · CertiK · 19 Apr 2024Open

Addresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=344 rewardToken = _rewardToken; ``` - `_rewardToken` is not zero-checked before being used.

Open the report
LowPotential Sandwich AttacksBiceps - audit · CertiK · 19 Apr 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. The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: - `routerV2.swapExactTokensForETHSupportingFeeOnTransferTokens()` - `routerV2.swapExactTokensForTokensSupportingFeeOnTransferTokens()` - `routerV2.addLiquidityETH{value: ethAmount}()`

Open the report
LowRedundant FalseBiceps - audit · CertiK · 19 Apr 2024Open

The use of `false` is redundant and does not affect the outcome, making the code less clear and potentially harder to maintain. Simplifying the condition to `if (_tatesPending > 0) {` enhances readability and maintains the intended functionality without unnecessary complexity. ```solidity=331 if (false || _tatesPending > 0) { ```

Open the report
LowThird-Party Dependency UsageBiceps - audit · CertiK · 19 Apr 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=43 IUniswapV2Router02 public routerV2; ``` - The contract `Biceps` interacts with third party contract with `IUniswapV2Router02` interface via `routerV2`.

Open the report
LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaBiceps - audit · CertiK · 19 Apr 2024Open

The return values of the `transfer()` and `transferFrom()` calls in the smart contract are not checked. Some ERC-20 tokens' transfer functions return no values, while others return a bool value, they should be handled with care. If a function returns `false` instead of reverting upon failure, an unchecked failed transfer could be mistakenly considered successful in the contract. ```solidity=192 IERC20(rewardToken).transferFrom(msg.sender, address(this), amount); ``` --- ```solidity=13 IERC20(tokenAddress).transfer(owner(), amount); ```

Open the report
LowVariables That Could Be Declared as ImmutableBiceps - audit · CertiK · 19 Apr 2024Open

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.

Open the report

Contracts1

AddressChainSource code
0x8e5cb7626dd949dff56fe2c130b75a8b6f1a05f8Chain: BNB ChainSource code: Verified source

Biceps Coin: questions

Is Biceps Coin audited?

Trustblock holds 1 public audit report for Biceps Coin, dated 19 Apr 2024. The latest is by CertiK (“Biceps - audit”).

Who audited Biceps Coin?

CertiK wrote the report Trustblock holds for Biceps Coin.

Are there open findings in Biceps Coin’s audits?

12 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 9 low (9 open, 3 acknowledged). 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="biceps-coin"
></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