GMO Internet says it will not pay hackers $50 million after server breach
Published Updated 1 new report since it was first published
GMO Internet said it refused a $50 million demand after hackers breached its Onamae.com Desktop Cloud service, and the company said up to 26,739 servers may be affected. After GMO did not pay, hackers posted alleged customer data, while FXTF blocked all logins from outside Japan.
What this rests on
What it means
GMO Internet sits at the center of a Japanese trading and hosting incident that combines server compromise with brokerage access. Onamae.com Desktop Cloud is the service named in the breach, and the Oct. 26 statement shows the company addressing the event publicly while the situation was still unfolding. The mention of customer brokerage accounts signals that this was not limited to ordinary server disruption.
For users and brokers, the immediate effect is tighter access and a review of account activity. FXTF’s decision to block all logins from outside Japan shows how a firm can respond by narrowing entry points when trading accounts are exposed. Customers who use remote access or travel outside Japan may now face a different login experience, while firms have to reassess how they authenticate and monitor sessions.
This case highlights the pressure placed on firms when attackers mix ransom demands with publication of alleged data. A refusal to pay leaves companies dealing with the release of information and the operational fallout at the same time, while a payment would have set a different precedent for future intrusions. The trade-off here is between resisting extortion and limiting exposure of customer material, and the incident puts both priorities in conflict.
Still open are the scope of the compromise and which customer records, if any, were actually taken or altered. GMO’s estimate of affected servers and the reports of unauthorized trades leave key questions about the reach of the breach, and FXTF’s response does not answer whether other brokers will take similar steps. A fuller accounting would need confirmation of what data was posted, which accounts were touched, and how many systems were involved.
Market reaction
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
How the story was built
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 2 months ago | Nesa incident | $50M |
| 1.7 years ago | Infini incident | $50M |
| 2.0 years ago | Radiant Capital incident | $50M |
| 5.9 years ago | Saffron Finance incident | $50M |
| 8.7 years ago | Blockchain.info · Phishing attack incident | $50M |
4230 incidents stored · 126 were as large as this one or larger ($50M)