GMO shuts down its Desktop Cloud after a breach that may reach 26,739 servers: if you keep secrets on a rented server, rotate them
GMO Internet confirmed on 20 Oct 2026 that attackers put malicious software on some customer servers of its Onamae.com Desktop Cloud. Up to 26,739 servers may be affected and unauthorized trades were reported. Here is what is confirmed, what is not, and what to check.
How urgent
Plan this week
Who is affected
Customers of Onamae.com Desktop Cloud by GMO (a rented Windows server service used mostly by forex traders), and anyone who keeps passwords, API keys or trading logins on a rented remote desktop
What to do
If you used Desktop Cloud, rotate every password and key stored on the server and check your accounts for trades or logins you did not make. If you keep secrets on any rented remote desktop, move them to a password manager or a secrets store and rotate them
Published 30 Oct 2026 · Sources last checked 30 Oct 2026No. 23 / 87
What happened
GMO Internet, a large Japanese hosting and domain company, began investigating on 19 October 2026 after a customer inquiry. On 20 October it confirmed that an unauthorized third party had installed malicious software in some customer server environments of Onamae.com Desktop Cloud, a rented Windows server service used mostly to run automated forex trading. On 21 October it began shutting down all Desktop Cloud servers, and the service remains interrupted.
GMO says up to 26,739 servers may have been affected. That is an upper limit, not a confirmed count of compromised servers. According to Euronews, trades were placed without account holders' permission at more than 70 securities and forex firms in Japan and abroad, and customer data was taken. GMO says it will cover the losses from unauthorized trades and pay ¥5,000 to every current Desktop Cloud customer. It says it will not pay the attackers and is working with the police.
Who is affected
- Desktop Cloud customers. BleepingComputer reports that data on the affected servers may have been exposed. Card details are stored on separate systems and were reported as unaffected.
- Anyone who kept trading logins on those servers. The Next Web notes that stored logins may have been exposed, and OANDA Japan warned its customers that logins for its trading platforms may have been exposed.
- Everyone else: a rented remote desktop that holds your keys and logins is a single place to lose them all.
What to do
Our advice, not GMO's:
- If you used Desktop Cloud, rotate every password, API key and trading login stored on the server, starting with brokers and exchanges. Do it from a device you trust.
- Check your accounts for trades, withdrawals or sign-ins you did not make, and set limits where the platform allows it.
- Expect phishingPhishing A message or page that pretends to be someone you trust to get you to hand over a password, a code or a payment. Tap again to open the glossary. GMO says it never asks for passwords or card details by email or phone. Use only the contact details you typed yourself.
- Keep secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary off rented remote desktops. Use a password managerPassword manager An app that creates, stores and fills in a different strong password for every account, so you only remember one. Tap again to open the glossary or a secrets store, and give each tool its own key with the smallest permissions.
If you build with AI tools
Our advice, not from the reports: treat any shared or rented machine as untrusted. Do not paste keys into a remote desktop, give every automation its own key with spending limits, and have a written list of where each key lives so that you can rotate them in an hour.
What we could not confirm
We have not read GMO's own notices directly; the facts come from press reports. How the attackers got in and who they are have not been published. The ransom is reported differently: Euronews says attackers reportedly asked for 50 million dollars in cryptocurrency, The Next Web gives no amount, and a figure of 1 million dollars that circulates on social media does not appear in the reports we read, so we do not use it. The number of servers actually compromised is not known: 26,739 is the number that may have been affected. GMO has said it will publish more details of its loss claims process, and we will update this page when it does.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- Euronews: Japanese company to compensate users hit by cyberattack (26 Oct 2026, press report) (opens in a new tab)
- BleepingComputer: Japan's Onamae Desktop Cloud hacked, up to 27,000 servers affected (21 Oct 2026, press report) (opens in a new tab)
- The Next Web: GMO asks Japan to use new cyber defence powers after hack (Oct 2026, press report) (opens in a new tab)
- Nippon.com: GMO Asks Govt to Take Active Cyber Defense Measures (24 Oct 2026, press report) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.