MEXC's response | ignored
MEFAI dont ignore community!
Every finding. Every submission. Every response. And what we're asking for now.
In March 2026 we began a security audit of MEXC Global. What started as a single exchange review expanded to three exchanges when we discovered shared infrastructure and identical credentials across MEXC, KCEX, and LBank.
The audit ran for 3 weeks. The methodology | public API analysis, DNS reconnaissance, APK, open source SDK review. Zero unauthorized access. We cannot disclose most details for security reasons, as they could pose a danger in the hands of malicious actors. We also informed these exchanges that we are not seeking a bounty. We allowed a specific period for the issues to be resolved, yet everything remains the same. People should know why they are using an exchange. Zero disclosure. They do not even feel the need to provide an explanation. Even test environments and production codes are intertwined.
Everything we found is independently verifiable.
The self referencing oracle, one curl command to the public API.
The bot signatures, one curl command to the trade endpoint.
The shared credentials, one curl to https://t.co/vp6Tjf2Dhw.
The undisclosed domains: one dig command each. The signature flaw: read MEXC's own SDK on GitHub. The APK findings: download, decompile, grep. No special access required. No tools beyond curl, dig, and apktool. What we are asking for,
@MEXC
Add external price oracles to all futures contracts. Zero self only contracts. Cap leverage at industry standard levels. 1000x is indefensible. Implement 2FA on withdrawal API. Make fund password mandatory. Include HTTP method and path in API signatures. Fix TrustAllCerts. Enable certificate pinning. Remove exported debug activities from production APK. Rotate all exposed credentials (OPS token, Sentry DSN, API keys). Disclose all operational domains in Terms of Service. Put internal tools behind VPN. Remove CVV via e mail.
@KCEX
Disclose the MEXC relationship to users. Rotate shared credentials. Get your own Sentry. Your own auth backend. Fix both dangling CloudFront CNAMEs before someone claims them. To
@LBank_Exchange
Explain why your app calls MEXC's infrastructure. Disclose the relationship in Terms of Service.
@SBF_FTX Show me your post about Gaza ( Palestinians) before you complain of Iranians' nuclear program .
You all kept quiet over the genocide in Gaza but are complaining of the world's most civilised nation
You damaged our investment to zero just to enrich yourself. Better behave