Meflex Token

CertiK2 addresses on BNB Chain

Audit

CertiK reviewed MEFLEX (Meflex Token) on 18 Mar 2024: 2 findings, 0 critical; all acknowledged, none fixed.

No open critical findings
Open the reportOpen MEFLEX’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings2

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium000
Low000
HighCentralization Risks in Ownable.solAcknowledged

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)

HighInitial Token DistributionAcknowledged

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.

Contracts in scope2

AddressChainSource code
Chain: BNB ChainSource code: Verified source
Chain: BNB ChainSource code: Verified source

Part of MEFLEX’s security record

MEFLEX
Audits1 audit by 1 firmLast audit Mar 2024, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open MEFLEX’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 reports · latest May 2025

See CertiK’s audits

Something 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