MEFLEX contract 0xa25b…0486 on BNB Chain

0xa25b23ff62142fb901f8fe26ecd90b9c00ee0486

As of 21 Nov 2026, Trustblock’s record holds 0xa25b23ff62142fb901f8fe26ecd90b9c00ee0486 on BNB Chain as a contract of MEFLEX. 1 audit report on Trustblock lists this address: CertiK, 18 Mar 2024. 2 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
Meflex TokenCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports2

2 High. In the firm’s own words; statuses are the firm’s, from each report.

HighCentralization Risks in Ownable.solMeflex Token · CertiKAcknowledged

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 and transfer the ownership to one of his EoAs or renounce the ownership. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ee-7414-dbc62d30-ad48-8572b257f72f/diagrams/centralization_Ownable-Ownable-_owner.svg)

The audit on Trustblock · Open the report
HighInitial Token DistributionMeflex Token · CertiKAcknowledged

All of the `MEF` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

The audit on Trustblock · Open the report

The MEFLEX security record · Every MEFLEX address · This address on the explorer