HashBit

In the contract `AntiBotBABYTOKEN` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority.  In the contract `BABYTOKENDividendTracker` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority.  In the contract `DividendPayingToken` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority.  In the contract `OwnableUpgradeable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority.  In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. 

The `swapAndLiquify` function converts half of the `swapTokens` to BNB. The other half of `swapTokens` and part of the converted BNB are deposited into the `AntiBotBABYTOKEN-BNB` pool as liquidity. For every `swapAndLiquify` function call, a small amount of BNB leftover in the contract. This is because the price of `AntiBotBABYTOKEN` drops after swapping the first half of the `AntiBotBABYTOKEN` tokens into BNBs, and the other half of `AntiBotBABYTOKEN` tokens require less than the converted BNB to be paired with it when adding liquidity. The contract doesn't appear to provide a way to withdraw those BNB, and they will be locked in the contract forever.