$BAKE [BurntCake] Token

Reentrancy in BURNTCAKE.claimCAKE(address) (#1113-1147):
External calls:
- _pancakeRouter.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,addr,block.timestamp) (#1139-1143)
State variables written after the call(s):
- _isWithdrawing = false (#1146)
Apply the check-effects-interactions pattern.

Additional information: link

BURNTCAKE.TeamReleaseLiquidity() (#1427-1437) ignores return value by liquidityToken.transfer(TeamWallet,amount) (#1435)
Use SafeERC20, or ensure that the transfer/transferFrom return value is checked.

Additional information: link

Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)

BURNTCAKE.claimCAKE(address) (#1113-1147) uses a dangerous strict equality:
- amount == 0 (#1130)
Don't use strict equality to determine if an account has enough Ether or tokens.

Additional information: link

Combination 3: Reentrancy vulnerabilities + Unchecked transfer vulnerability. Usual for scams. May be justified by some complex mechanics (e.g. rebase, reflections). DYOR & manual audit are advised.

BURNTCAKE.TeamRemoveLiquidity(bool) (#1439-1468) ignores return value by _pancakeRouter.removeLiquidityETHSupportingFeeOnTransferTokens(address(this),amount,0,0,address(this),block.timestamp) (#1452-1459)
Ensure that all the return values of the function calls are used.

Additional information: link

BURNTCAKE._approve(address,address,uint256).owner (#1521) shadows:
- Ownable.owner() (#246-248) (function)
Rename the local variables that shadow another component.

Additional information: link

BURNTCAKE.TeamUpdateLimits(uint256,uint256) (#1380-1397) should emit an event for:
- balanceLimit = newBalanceLimit (#1395)
- sellLimit = newSellLimit (#1396)
Emit an event for critical parameter changes.

Additional information: link

BURNTCAKE.SetupLiquidityTokenAddress(address).liquidityTokenAddress (#1409) lacks a zero-check on :
- _liquidityTokenAddress = liquidityTokenAddress (#1410)
Check that the address is not zero.

Additional information: link

Reentrancy in BURNTCAKE.transferFrom(address,address,uint256) (#1529-1537):
External calls:
- _transfer(sender,recipient,amount) (#1530)
- _pancakeRouter.addLiquidityETH{value: bnbamount}(address(this),tokenamount,0,0,address(this),block.timestamp) (#1213-1220)
- _pancakeRouter.swapExactTokensForETHSupportingFeeOnTransferTokens(amount,0,path,address(this),block.timestamp) (#1201-1207)
- _pancakeRouter.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,addr,block.timestamp) (#1139-1143)
External calls sending eth:
- _transfer(sender,recipient,amount) (#1530)
- _pancakeRouter.addLiquidityETH{value: bnbamount}(address(this),tokenamount,0,0,address(this),block.timestamp) (#1213-1220)
- _pancakeRouter.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,addr,block.timestamp) (#1139-1143)
State variables written after the call(s):
- _approve(sender,msg.sender,currentAllowance - amount) (#1535)
- _allowances[owner][spender] = amount (#1525)
Apply the check-effects-interactions pattern.

Additional information: link

Reentrancy in BURNTCAKE.transferFrom(address,address,uint256) (#1529-1537):
External calls:
- _transfer(sender,recipient,amount) (#1530)
- _pancakeRouter.addLiquidityETH{value: bnbamount}(address(this),tokenamount,0,0,address(this),block.timestamp) (#1213-1220)
- _pancakeRouter.swapExactTokensForETHSupportingFeeOnTransferTokens(amount,0,path,address(this),block.timestamp) (#1201-1207)
- _pancakeRouter.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,addr,block.timestamp) (#1139-1143)
External calls sending eth:
- _transfer(sender,recipient,amount) (#1530)
- _pancakeRouter.addLiquidityETH{value: bnbamount}(address(this),tokenamount,0,0,address(this),block.timestamp) (#1213-1220)
- _pancakeRouter.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,addr,block.timestamp) (#1139-1143)
Event emitted after the call(s):
- Approval(owner,spender,amount) (#1526)
- _approve(sender,msg.sender,currentAllowance - amount) (#1535)
Apply the check-effects-interactions pattern.

Additional information: link

BURNTCAKE.TeamRemoveRemainingBNB() (#1470-1475) uses timestamp for comparisons
Dangerous comparisons:
- require(bool,string)(block.timestamp >= _liquidityUnlockTime,Not yet unlocked) (#1471)
Avoid relying on block.timestamp.

Additional information: link

Address._verifyCallResult(bool,bytes,string) (#447-464) uses assembly
- INLINE ASM (#456-459)
Do not use evm assembly.

Additional information: link

EnumerableSet.remove(EnumerableSet.UintSet,uint256) (#727-729) is never used and should be removed
Remove unused functions.

Additional information: link

BURNTCAKE.sellLimit (#804) is set pre-construction with a non-constant function or state variable:
- _circulatingSupply
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Additional information: link

solc-0.8.4 is not recommended for deployment
Deploy with any of the following Solidity versions: 0.5.16 - 0.5.17, 0.6.11 - 0.6.12, 0.7.5 - 0.7.6 Use a simple pragma version that allows any of these versions. Consider using the latest version of Solidity for testing.

Additional information: link

Low level call in BURNTCAKE.TeamRemoveRemainingBNB() (#1470-1475):
- (sent) = TeamWallet.call{value: (address(this).balance)}() (#1473)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence

Additional information: link

Constant BURNTCAKE.DistributionMultiplier (#1000) is not in UPPER_CASE_WITH_UNDERSCORES
Follow the Solidity naming convention.

Additional information: link

Variable IPancakeRouter01.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountADesired (#86) is too similar to IPancakeRouter01.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountBDesired (#87)
Prevent variables from having similar names.

Additional information: link

BURNTCAKE.slitherConstructorConstantVariables() (#762-1555) uses literals with too many digits:
- InitialSupply = 1000000000000 * 10 ** _decimals (#780)
Use: Ether suffix, Time suffix, or The scientific notation

Additional information: link

TeamRemoveRemainingBNB() should be declared external:
- BURNTCAKE.TeamRemoveRemainingBNB() (#1470-1475)
Use the external attribute for functions never called from the contract.

Additional information: link

Contract ticker ($BAKE) contains non-alphanumeric characters.
Not a direct threat, but may indicate unreliable intentions of developer. Non-alphanumeric chars (,.;!#*&") are extremely rare among low risk tokens.

Number of Binance Smart Chain (BSC) token holders is less than 100. Token is either dead or inactive. Ignore for presale.

Average PancakeSwap trading volume, liqudity, number of swaps are extremely low. Token seems to be dead.

Token is deployed only at one blockchain

Token has only one trading pair

Unable to find PancakeSwap trading pair to compute liquidity.

Unable to find PancakeSwap trading pair to compute volume.

Unable to find PancakeSwap trading pair to compute number of swaps.

Unable to find website, listings and other project-related information

Token has no active CoinGecko listing / rank

Token has no active CoinMarketCap listing / rank

Young tokens have high risks of price dump / death