GMO Internet Cloud Breach: What Is Confirmed and What Is Claimed About ARTEX

GMO Internet Group confirmed that attackers breached its Onamae.com Desktop Cloud service, which hosts up to 26,739 Windows virtual private servers used by retail foreign-exchange traders, and used stolen brokerage credentials to place unauthorized orders, according to the company's fourth and fifth notices. GMO confirmed a ransom was demanded and said it refused to pay; one customer reported losing more than 4 million yen in two seconds, while the attackers' claim of about 7.7 billion yen remains unconfirmed. The AI angle rests on a reported statement by GMO's CEO pointing to an autonomous AI penetration-testing tool called ARTEX, a claim the public record does not detail, while GMO Cybersecurity separately reported six overseas servers running ARTEX tied to attacks on Japanese financial and logistics firms.

GMO Internet Group has confirmed that attackers breached its Onamae.com Desktop Cloud, a rented Windows server service that retail foreign-exchange traders use to run automated trading tools, and then used stolen credentials to place unauthorized orders at brokerages. The company says up to 26,739 servers could have been affected. The AI angle comes from the group's CEO, who reportedly pointed to an autonomous AI penetration-testing tool called ARTEX. That part needs careful reading, because the public record supports a narrower claim than some headlines do. This post separates what GMO and the press have confirmed from what is only claimed, lays out the timeline, and ends with what customers and engineers can do. It sits next to our earlier coverage of Japan's run of cyberattacks https://explainx.ai/blog/japan-cyberattacks-september-2026-times-car-gyazo-keio-monogatari-explained and our running October 2026 attacks tracker https://explainx.ai/blog/october-2026-cyberattacks-list-breaches-exploits-ai-run-attacks-tracker-2026 . Quick answers: confirmed vs claimed | Question | Status | Answer | |---|---|---| | Was the service breached? | Confirmed by GMO | Malicious programs were found on customer server environments of Onamae.com Desktop Cloud | | How many servers? | Potential, not confirmed | 26,739 servers "could be affected" per GMO's fifth notice | | Were customers' brokerage accounts traded without consent? | Confirmed by GMO | Yes, using credentials stored by trading tools on the servers | | Total losses? | Not public | One customer reported more than 4 million yen lost in two seconds; the attackers' claim of about 7.7 billion yen is unconfirmed | | Was ransom demanded? | Confirmed by GMO | Yes; GMO says it refused to pay | | Was ARTEX used in this breach? | Claimed | Reported as the CEO's statement; intrusion route not publicly detailed | | Was ARTEX used against other Japanese firms? | Reported by GMO Cybersecurity | Six overseas servers running ARTEX tied to attacks on Japanese financial and logistics firms | What is Onamae.com Desktop Cloud, and why did the breach hit brokerage accounts? According to a translated analysis from Lilting https://lilting.ch/en/articles/gmo-active-cyber-defense-request?ref=explainx , which draws on GMO's own notices, Onamae.com Desktop Cloud rents Windows virtual private servers so customers can run FX auto-trading tools such as MetaTrader 4 and 5 around the clock. Those tools store the login ID and password for each customer's brokerage account. The servers therefore hold the keys to accounts that live at brokers and FX firms, not at GMO. That design explains the blast radius. Shutting down GMO's servers did not stop an attacker who already held the credentials from placing orders from elsewhere. It is the same lesson we keep seeing with agent and automation platforms: a convenience layer that stores long-lived secrets becomes the target. Our coverage of AI agents moving into financial accounts https://explainx.ai/blog/citi-bank-of-america-jpmorgan-block-ai-agents-customer-accounts-deposit-risk-2026 makes the same point from the bank side. Timeline from GMO's notices The dates below come from the Lilting translation of GMO's fourth and fifth notices. All times are JST. | Date | Event | |---|---| | Oct 19 | Investigation starts after a customer inquiry | | Oct 20 | Malicious programs planted by a third party found on some servers; new sign-ups and control panel suspended | | Oct 21, 04:00 | All server plans shut down in sequence; first notice published | | Oct 21 onward | Customers report operations they did not make in their trading accounts | | Oct 22 | GMO consults police; second notice says credentials may have been obtained and used without authorization | | Oct 24, 11:50 | Fourth notice announces compensation and a request to the government | The first notice had said GMO had not confirmed misuse of the viewed information. The second notice changed that, which is worth remembering when judging early incident statements: they are often revised within days. What did the attackers demand? GMO disclosed that people believed to be the attackers demanded money. As relayed in the Lilting translation, the threats were to keep placing unauthorized orders at more than 70 brokers and FX firms in Japan and abroad, to publish information about the service and about customer PCs that had connected to it and carry out a ransomware attack, and to publish information about GMO's systems and operations. GMO said it would not pay and handed communication records to the police cybercrime unit. One customer interviewed by TBS saw a balance drop to zero on October 21, with losses of more than 4 million yen within two seconds. A sender calling itself "HackingTeam" then emailed that customer, per TBS as summarized by Lilting. A claim-of-responsibility site reportedly said the group had destroyed accounts worth about 7.7 billion yen in 24 hours. That is the attacker's claim, and the real damage has not been confirmed. What is the ARTEX claim, exactly? There are two separate threads, and they should not be merged. Thread one: GMO Cybersecurity's finding October 19-20 . Jiji Press via Nippon.com https://www.nippon.com/en/news/yjj2026102000795/?ref=explainx reported that GMO Cybersecurity by Ierae, a GMO Internet Group subsidiary, traced cyberattacks on Japanese companies to six servers, all of which used Artex, an AI-powered penetration-testing tool. The attacks from those servers targeted Japanese financial and logistics companies, eight of which disclosed information breaches between September and October. GMO Cybersecurity said multiple incidents were caused by the same group. Jiji also reported that Artex is believed to have been used against South Korean financial institutions. Other outlets describe ARTEX as a Chinese-developed, LLM multi-agent tool; those secondary details come from press coverage we could not open directly, so treat them as reported. Thread two: the CEO's statement October 24-25 . Secondary reports, such as this one from OfficeChai https://officechai.com/stories/the-internet-is-breaking-down-says-japans-gmo-internet-group-ceo-after-hackers-hijack-its-cloud-servers-to-run-unauthorized-fx-trades/?ref=explainx , say Masatoshi Kumagai blamed misuse of ARTEX and warned about AI misuse. We could not open that report or the original interview, and in our searches no readable source tied ARTEX to the Onamae.com Desktop Cloud intrusion. We also found no public GMO notice detailing how the intrusion began. Treat the CEO link as unconfirmed. So the careful statement is this: GMO's security subsidiary has publicly tied an AI pentesting tool to attacks on Japanese firms, and the group's CEO links the broader wave to AI misuse. What is not yet public is evidence that ARTEX performed the specific intrusion into Onamae.com Desktop Cloud, or which vulnerability was used. Sources do not yet agree on loss totals, and the 26,739 figure is a potential count. Why this matters beyond Japan An autonomous pentesting agent is a dual-use product. The same capability that lets a defender find weaknesses lets an attacker scale reconnaissance and exploitation. This is the pattern behind AI agents targeting Latin American financial firms https://explainx.ai/blog/cybercartel-ai-agents-claude-grok-kimi-400-latin-american-financial-targets-straiker-what-is-confirmed-2026 , and it fits warnings from Bill Gates about AI-driven cyberattacks https://explainx.ai/blog/bill-gates-cnn-ai-cyberattacks-negative-surprises-next-year-crowdstrike-89-percent-2026 and the G7 finance tabletop exercises on AI cyberattacks https://explainx.ai/blog/g7-finance-tabletop-exercises-ai-cyberattacks-katayama-imf-bangkok-2026 . It also shows the limit of an "AI did it" explanation. Whatever role ARTEX played, the design stored credentials where one compromise exposed everything. AI raises the tempo; basic patching and secret hygiene still decide the outcome. Japan's active cyber defense: what GMO asked for On October 24 GMO asked the government to apply "active cyber defense" and called the incident the first activation case. Per Lilting, the framework lets police and the Self-Defense Forces access servers used in attacks and neutralize them, and the relevant part took effect on October 1, 2026. Neutralization means deleting malicious programs or changing settings on a server, not physically destroying it. The police clause does not require the attacker to be a state, and it covers serious harm to people's property when there is an urgent need. But there is no procedure for a private company to apply; GMO's request is input to a government decision. For servers abroad, the National Security Council reviews a response policy, the Foreign Minister is consulted, and an independent oversight commission approves in advance. As of 17:00 JST on October 24, no government response had been found. Neutralization also cannot restore balances already lost; losses are handled through GMO's compensation and the brokers. What GMO is offering customers Per the fourth notice as relayed by Lilting: a flat 5,000-yen payment to every current user of the service, compensation for realized losses from unauthorized trades, and six months of free use of a replacement service on a separate cloud platform. GMO asks customers to contact their brokers about cancelling trades or getting refunds, and says it will pay whatever remains after any refund. How to protect yourself If you used the service or a similar hosted trading setup: 1. Change the brokerage password, then terminate all active sessions or ask the broker to disconnect them. GMO warns earlier connections may remain active after a password change. 2. Enable multi-factor authentication and API or IP restrictions where your broker offers them. 3. Review recent trades and contact your broker promptly about disputed orders. 4. Treat any machine that connected to the affected service as potentially exposed and rotate other credentials stored on it. 5. Be wary of emails claiming to be from the attackers or from GMO; verify through official notices. If you run cloud or agent infrastructure: - Close known findings quickly. An unpatched vulnerability is the cheapest way in. - Do not keep long-lived brokerage, payment or admin credentials on a shared server; use scoped, revocable tokens. - Assume attackers have automation. Monitor for rapid, scripted actions such as many orders within seconds. - For AI coding and operations agents, put guardrails on what they may do. AgentBeam https://agentbeam.com/?ref=explainx , the agent security platform from the explainx.ai team, stops AI agents before they take dangerous actions. What to watch next - A GMO root-cause disclosure naming the vulnerability and whether ARTEX was used on this intrusion. - Final loss figures and how many of the 26,739 servers were actually compromised. - Whether the government activates neutralization, and against servers in which country. - Whether the developer of ARTEX restricts the tool further. Press coverage says it halted updates, which we could not verify directly. - Whether brokerages add controls for sessions that originate from hosted VPS environments. Accurate as of October 25, 2026, based on GMO's notices as relayed by secondary outlets and on Jiji Press reporting. We could not open GMO's original notices directly; figures may change as the investigation continues.