CertiK reviewed Birb.com (Birb - Audit 1) on 10 Sep 2024: 17 findings, 0 critical; 14 marked fixed, 3 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 2 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 0 | 14 |
In the contract `BirbV4` the role `CEO` has authority over the functions shown in the diagram below. Any compromise to the `CEO` account may allow the hacker to take advantage of this authority and wipe the contract address of all its tokens, set the `marketingWallet` and `tokenWallet` to addresses he/she controls, which are used to collect taxes, and use the `airdropToWallets()` function to send a large amount of tokens to addresses he/she controls.  ---- In the contract `BirbV3ToV4Migration` the role `CEO` has authority over the functions shown in the diagram below. Any compromise to the `CEO` account may allow the hacker to take advantage of this authority and wipe the contract address of all its tokens, as well as set the `tokenOut` contract to a malicious contract address, which can be used to reenter the contract.  --- **UPDATE: 09/10/2024** In the contract `BIRBBASEv2`, 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 and set the birb wallets, rescue specified token, remove the last pair, set tax status for an address, add a new pair, set sell tax rates, set the buy tax parameters, set swap threshold limit, and rescue the contract's ether. 
All of the `BIRB` tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute `BIRB` tokens without obtaining the consensus of the community.
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.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (2)
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething 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