BNB (ERC20) (BNB) Smart Contract Risk
Missing Return Data
⚠ HIGH severityVulnerability
BNB ERC20 token does not return a boolean on transfer, causing reverts in standard ERC20 interface calls.
Related: Unchecked Return Values
Safe integration
Use OpenZeppelin SafeERC20 (safeTransfer) to handle tokens that do not return data.
Contract addresses
| Chain | Address |
|---|---|
| Ethereum | 0xb8c77482e45f1f44de1745f52c74426c631bdd52 |
Audit any contract that interacts with BNB: SmartContract.us automatically detects BNB integration risks →
Chain & standard security guides
What this contract permits today
Read live from Ethereum on 2026-10-14. This is a different question from the integration risk above: not how to call the token safely, but what the holders of its keys are able to do to the people holding it.
| Question | Answer |
|---|---|
| Can new tokens be created? | No |
| Can transfers be blocked? | No |
| Is there a trading tax? | No |
| Can the logic be replaced? | No |
| Can liquidity be withdrawn? | Yes |
The permissions above rest with 0x00C5E04176d95A286fccE0E68c683Ca0bfec8454, a single private key rather than a multisig or a timelock. Whether that is acceptable depends on who holds it.