BNBREW (BNBREW) security report
Radar AI scanned BNBREW on BNB Smart Chain. The verified token has fixed construction-time supply and no owner, tax, blacklist, pause, upgrade, or post-deployment mint controls. One medium-severity risk remains: the full configured supply is assigned to one constructor recipient without vesting or lock enforcement.
No critical or high-severity exploit was identified in the verified source. A medium-severity allocation and centralization risk exists because the constructor mints the complete configured supply directly to a single recipient, with no vesting or lock mechanism in the token contract.
Trust score: 84/100. Source verified: Yes. Chain: bsc. Contract: 0x749ab78ba2074af5e64b681ca51be994ec1d0eac.
This report was last modified on 2026-10-07 and contains 1 material finding.
medium finding: Entire initial supply is assigned to one constructor recipient
The constructor calls _mint(recipient_, totalSupply_), assigning the complete configured supply to one address at deployment. The token contract provides no vesting, timelock, distribution limit, or transfer restriction for that allocation. If the deployment recipient is not independently controlled or the allocation is not transparently managed, a single address can transfer its entire allocation without contract-level constraints.
Evidence: In BrewToken.sol, the constructor accepts totalSupply_ and recipient_ and executes _mint(recipient_, totalSupply_). No vesting contract, lock, allocation schedule, or subsequent distribution control is implemented. The inherited ERC-20 transfer function permits the recipient to transfer its balance normally.
Recommendation: Document the initial allocation and recipient, and use an independently verified vesting or timelock contract when the tokenomics require restricted distribution. If unrestricted initial allocation is intentional, disclose that the token contract itself does not enforce distribution limits.