Broker Entity: Exness SC Ltd / Exness (EXOTReal SERVER Architecture)


Target Account ID: 10000265797


Hello Myfx book team,


I am forwarding you this thread to put the unredacted, microsecond-level production logs and database tables from my Exness account directly onto the public record. While Exness successfully convinced the industry-funded Financial Commission (FinCom) to dismiss my case by matching a static, macro-level device ID (cid), their own server-side plumbing reveals severe system anomalies, unauthorized internal access loops, and deliberate log truncation.


Line-by-line, here is the hard reality of what happened to my account, backed by the raw data attached.


THE SIX CRITICAL TECHNICAL & ADMINISTRATIVE ANOMALIES


1. THE IMPOSSIBLE 15-LOT UNAUTHORIZED TRADE (May 5, 2026).


•On May 5, 2026, my account had eight normal 0.10 lot trades running smoothly on a USD 1,000 balance.(0.10 ×3 on XAU and 0.10×5 on CHFUSD). At 03:36:59, an unauthorized 15-lot BUY order on XAUUSD was executed, at the backend wiping out my account via a Stop-Out in exactly 11 seconds.


• Exness claims "Unlimited Leverage" allows this massive 15-lot block to open on a tiny $1,000 retail balance. However, their own technical architecture makes this execution anomalous. Under Exness's institutional risk rules, Unlimited Leverage automatically downgrades and enforces dynamic margin caps for massive trade sizes or whenever an account's exposure threatens systemic balance protection. A 15-lot gold position represents multi-million dollar volume completely unsupported by a $1,000 balance. The fact that the engine forced this massive position open while live telemetry registered platform=undefined proves this was a rogue internal matching-engine injection that bypassed standard client-side terminal protocols and risk gateways.


2. UNAUTHORIZED ACCOUNT INFILITRATION (May 18, 2026)


•Immediately after FinCom formally acknowledged my dispute file on May 18, 2026, my account registered login loop attempt. This originated hundreds of miles away(Mbarara) from my true physical location (Kajansi) proving that internal actors breached the account the moment an official investigation began.


3. THE CORPORATE ADMIN TOKEN LEAK (May 19, 2026)


•On May 19, 2026, an external interaction generated a live administrative session token (tk=jwkTl8jmtM...) explicitly tied to an internal Exness corporate staff profile email address: [email protected].(attached)


• The Insider Link: This corporate email belonged to my officially assigned Client Relationship Manager since 2024. She directly generated and sent me a webinar invite link embedded with an administrative session token, providing absolute, un-falsifiable proof of internal corporate backdoors actively tracking and manipulating my live profile during an active dispute window.


4. SECONDARY LOGIN LOOP (May 21, 2026)


• On May 21, 2026, a secondary layer of unauthorized authentication ping hit my account from a completely different location (Jinja) . All these pings happened when I was static in one location (Kajansi ) proved by my Internet provider geo location logs.


5. THE 63-HOUR SERVER BLACK HOLE & LOG SPOLIATION 


•The official data package Exness forwarded to me after I officially requested, completely scrubbed the timeline between May 18 and May 21.


•While their servers were actively pinging my profile, the technical transaction data (component=extrade_oms_real) abruptly snaps mid-sentence: "...volume...". They executed a deliberate 63-hour database truncation to erase the audit trail of their internal logins, remote overrides, and metadata alterations.


6. THE POST HOLD- DISAPPEARANCE OF THE RELATIONSHIP MANAGER (The Cover-Up)


•As soon as I served Exness with a formal Litigation and Data Preservation Hold, my Client Relationship Manager— who sent the compromised webinar link and I believe held administrative access to my account—was abruptly and completely removed from my personal area without notice.


•Removing the dedicated staff member who has handled my account for years immediately after a legal hold was served is highly indicative of corporate evidence spoilation and It points to a deliberate attempt to clean up the paper trail before regulators.


7•ADMINISTRATIVE EVASION & SOVEREIGN OMBUDSMAN APPEAL.


* The Seychelles Financial Services Authority (FSA) on October 12, 2026 revealed that they have closed the file after submitting it on 11, July, 2026 (roughly 90 days of no communication) on a procedural technicality. The FSA couldn't even be bothered to open the case file. Closing the case solely because the initial complaint text was not routed to the single inbox '[email protected]'—despite having been in full communication with the Relationship Manager through an Exness's official email address which issued a final rejection on May 11 explicitly noting """Our decision towards this request remains unchanged and it is FINAL".


• In response to this refusal by the FSA to investigate documented unauthorized execution, data spoliation and evidence spoilation, a formal Maladministration Case was filed with the Office of the Seychelles Ombudsman to demand a mandatory structural audit of Exness’s web-server database extraction tables and evidence spoilation and I'm still waiting for their decision.


Because Exness " EXOTReal" infrastructure operates as a unified global technological framework, formal Data Breach and Market Manipulation files are also open with the UK Financial Conduct Authority (FCA), the UK Data (ICO)and Cyprus Data Commissioner's offices.


INFRASTRUCTURE FIELDS EXNESS MUST PUBLICLY CLARIFY.


To senior MYIFXBOOK team and technical auditors reading this, the system has blocked me from uploading Exness raw unredacted files to draw your attention to the following parameters hardcoded into the backend script outputs and I would request you to allow me share them by email.


•CONTEXT_TYPE_SYMBOL_ALWAYS_SLIPS / category: Slippage Always: Exness must explain why specific asset classes are hardcoded with profiling tags that systematically guarantee execution slippage, independent of live market liquidity.


• DELAY_TYPE_STATIC & RANDOMIZATION_APPROACH_TYPE_DURATION_BASED: This confirms the presence of an intentional, manufactured processing delay before an order is completed. Exness must clarify if this latency engine was weaponized against my account during the 15-lot liquidation event.


• platform=undefined (Retroactively overwritten to "MQ Client"): The original live telemetry shows an untraceable terminal state during the market crash. Exness appears to have retroactively overwritten this metadata in their defense reports to falsely blame a standard client-side MetaQuotes terminal.


•Artificial freezing and price injections.


PLEASE ALLOW ME TO SHARE ALL THE NECESSARY DOCUMENTS THAT HAVE BEEN BLOCKED BY THE SYSTEM VIA EMAIL FOR MYFXBOOK COMMUNITY TO ANYLYSE AND MAKE GOOD DECISIONS WHILE CHOOSING BROKERS.