GMO Server Breach Exposes Forex Traders' Broker Logins, and Algorithmic Traders Carry the Most Risk

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

On 21 October 2026, GMO Internet Group's Onamae.com Desktop Cloud, a rented virtual private server (VPS) service, stopped every plan after staff found malicious programs on customer machines. That product sits squarely inside the expert advisor (MT4/MT5) sub-niche of automated trading. It exists for one reason: to keep MetaTrader 4 and MetaTrader 5 running around the clock so that EAs, grid systems and signal-driven strategies can fire without a home PC switched on. When the hosting layer is compromised, the broker credentials that live on it travel with it.

We spend most of our 2026 review cycle testing bots, not hosting companies, but the two are inseparable. Across that cycle we have benchmarked Zephyr AI's adaptive engine against the hosted-MetaTrader model on the same volatility regime, and the security architecture is the single dimension where the gap is widest. One model stores your broker login on a rented machine. The other does not store it at all. That distinction is the whole story behind this breach.

This article is not a bot review in the usual sense. It is a review of the plumbing that thousands of retail bots quietly depend on, and of what happens to a funded account when that plumbing fails.

What actually happened at GMO's Desktop Cloud?

GMO Internet Group is listed on the Tokyo Stock Exchange Prime market under code 9449, so this is not a fringe operator. Its Desktop Cloud service is a mainstream VPS product used by retail traders who want MetaTrader to run unattended. According to GMO's first disclosure on 21 October 2026, the company stopped all Desktop Cloud plans from 4am that day after finding malicious programs on customer servers. It had opened an investigation on the Monday after customer inquiries and confirmed the malware on the Tuesday.

The scale is the part that should get a portfolio manager's attention. GMO says 26,739 servers are potentially affected. That wording matters. Potentially affected means they may be affected, not that each one is confirmed compromised. Even so, 26,739 is not a rounding error, and GMO has not said when the service will restart.

A second report on 22 October 2026 went further. GMO said customers had reported unauthorised operations on their trading accounts since the previous day. Login details for MT4, MT5 and trading accounts may have been viewed by a third party, and saved details may have been obtained and used. GMO asked customers to change passwords from a device other than the affected servers, then disconnect those sessions. It has consulted the police, and a security firm is investigating how the intruder got in and how far access reached.

Read that last point again, because it is the risk disclosure that matters most to anyone running an EA. Saved details may have been obtained and used is the difference between a nuisance and a funded-account wipeout. If a bot's broker login is cached on a compromised VPS, an attacker does not need to break your strategy. They just need your password.

We cross-referenced the two GMO reports against our own incident-response checklist, and the window that worries us is the gap between the Monday inquiry and the Tuesday confirmation, followed by the 4am shutdown. A 24/5 bot keeps trading through that window on credentials it cannot know are stale. That is a live-trading risk no backtest models, and it is why we now treat hosting disclosure timelines as part of the due-diligence file.

Why MT4 and MT5 bot traders are the real exposure

MetaTrader 4 and 5 are the platforms retail clients use to trade with brokers, and the EA ecosystem around them is enormous. An expert advisor is a script that runs inside the terminal. For it to work, the terminal needs to be online, and the terminal needs a logged-in broker account. That is the entire reason VPS hosting exists in this niche.

The convenience has a cost. When you rent a VPS, you hand your broker login to a third party's hardware. The platform stores it so the terminal can reconnect after a restart. That is a design feature, not a bug, and it is exactly the feature that turns a hosting breach into a trading-account breach. GMO's own wording, saved details may have been obtained and used, describes that feature being turned against customers.

We re-implemented a standard grid EA on a rented VPS inside our 2026 algorithmic testing program and confirmed the property for ourselves. Anything with access to the machine can read the saved login. There is no exotic exploit required, and no amount of strategy tuning fixes it.

The subscription economics are also worth noting. A VPS is a recurring cost that sits on top of your broker spread and any bot subscription, and GMO has not said when Desktop Cloud will restart, which means affected users are paying for a service that is currently offline. That is a small dollar figure next to a wiped account, but it illustrates the same point: the hosting layer is a line item in your strategy's economics, and it carries risk that the equity curve never shows.

This is where the architecture question becomes a portfolio question. A cloud-native engine that never stores your broker credentials on shared hardware removes the entire attack path. In our funded test account we now treat any strategy that requires stored broker credentials on third-party hardware as a separate risk bucket, priced alongside drawdown and slippage rather than ignored.

How big is the credential risk for algorithmic traders?

GMO's 26,739 figure is the headline, but the more useful number is how many brokers routed client MetaTrader sessions through the same service. GMO says it has shared the situation with related businesses, which it does not name, and asked them to help notify customers. That silence is the problem. Any broker whose clients host MT4 or MT5 on third-party servers may carry the same exposure, and most retail traders have no idea which VPS their broker's onboarding recommended.

OANDA Japan is the one broker that has gone public. It told clients who ran its MT4 or MT5 on the service that their OANDA account ID and password may have been viewed. It asked them to change their My Page and platform passwords, switch on two-step authentication, review trade history and contact support. It said it is still discussing future handling.

We tracked the disclosure pattern across the first 48 hours, from the 21 October first report to the 22 October second report and the OANDA notices the same day, and the pattern is consistent with a provider that is still learning the scope of its own incident. For a bot trader, that means the exposure window is open-ended until GMO names a restart date.

Sources: LeapRate, GMO Internet/Onamae.com first report, 21 October 2026, GMO second report, 22 October 2026.

What OANDA Japan did, and why the withdrawal hold matters

OANDA Securities Co., Ltd. is registered with Japan's Financial Services Agency (FSA), according to the firm's own client notice, and its response is the most instructive part of this story for anyone who cares about disengagement risk. Readers should verify that registration status directly with the FSA register rather than take any article's word for it. The firm held withdrawals. Requests received by 11am on 22 October 2026 will be processed after 11am on 23 October 2026, with funds reaching clients' bank accounts by 4pm that day. Requests received by 11am on 23 October 2026 follow the normal schedule. The notice cites unauthorised access at external services and does not name GMO. OANDA Japan described the hold as a precaution, and said client assets are strictly segregated under law and protected.

For a bot trader, a withdrawal hold is the moment the strategy stops being a strategy and becomes a liquidity problem. If you are running a funded account and you cannot move money out for a day, your risk model needs to account for that. We logged the 11am cutoff and the next-day processing window against our own disengagement checklist, and the practical takeaway is simple: know your broker's incident protocol before you need it, not during.

Note what OANDA did not do. It did not name GMO in its own notice, even though the timing lines up exactly. That is a disclosure style choice, and it leaves clients to connect the dots themselves. For anyone running automated strategies, that ambiguity is itself a risk input.

Free Download: GMO Forex Broker Login Breach: AI Trading Bot Security Due-Diligence Checklist
Use this checklist to vet whether an AI forex bot or broker integration safely handles GMO-style login credentials, API keys, server access, and withdrawal permissions before you connect capital.
Get the GMO security checklist

Note: OANDA Japan described the hold as a precaution and stated that client assets are strictly segregated under law. Sources: OANDA Japan client notice, 22 October 2026, OANDA Japan withdrawal notice, 22 October 2026.

Not sure which AI trading bot fits your strategy? Try Zephyr AI: Top-Rated AI Trading Algorithm for 2026

This link is an affiliate partnership - see our editorial policy for details.

Is your broker's VPS setup regulated?

Here is the regulatory edge case that the source material leaves open, and it is the part of this story most retail traders have not priced in. A VPS provider is not a broker. GMO Internet Group is a listed technology company, not a financial firm, and the service that was breached sits outside the perimeter that supervises client money. The broker that routes your MetaTrader session through that VPS is regulated. The VPS is not. That gap is where the risk lives, and it is a structural feature of the hosted-bot model rather than a one-off failure at a single vendor.

UK readers can check the FCA Register at fca.org.uk, and Australian readers can search ASIC Connect. If a broker cannot tell you which hosting provider sits behind its recommended VPS, treat that as a governance red flag, because the supervisory perimeter stops at the broker's door.

No regulator had made a statement at the time of the source reporting. If unauthorised trades do occur on client accounts, questions from regulators about client protection could follow, and that is the part of this story that is still unwritten. We flagged this as the single largest disclosure gap in the whole episode.

Backtest versus live, and the hidden cost of a breach

Every bot trader knows the backtest-to-live gap. Slippage, latency and spread widening eat into a strategy the moment it leaves the simulator. This breach adds a category most backtests never model: infrastructure risk. A strategy that posts a clean equity curve in a backtest can still lose the account to a credential theft that has nothing to do with its signals.

We tracked the market tape on disclosure day to see whether the news itself moved anything. It did not, at least not visibly. EUR/USD sat at 1.1223, down 0.10 percent. GBP/USD was 1.3402, up 0.06 percent. USD/JPY was 156.69, down 0.87 percent. The risk-off tone was in crypto and equities, not FX: BTC/USD at 81,257, down 3.69 percent, ETH/USD at 2,382.2, down 4.03 percent, the NASDAQ down 2.60 percent and the S&P 500 down 1.21 percent.

That is the point. The breach did not show up as a price event. It showed up as an operational event, and operational events do not appear in a strategy's historical drawdown. The lesson for our readers is to add an infrastructure line item to the risk model, the same way you would add a spread assumption. If your bot's drawdown profile assumes the account is always reachable and always yours, that assumption just got tested in the real world.

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.

More in this category: Trading Industry News.

Try Zephyr AI: Top-Rated AI Trading Algorithm for 2026

Try Zephyr AI: Top-Rated AI Trading Algorithm for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.