GMO asked Onamae.com Desktop Cloud customers to disconnect and power down their PCs after an intruder threatened a ransomware attack. Its October 28 follow-up now asks customers to scan and back up before reusing PCs, as detailed in the update below. Account protection remains a separate task.
Bill Toulas’s October 27 report describes the escalation. GMO’s October 27, 13:55 notice separates two developments: someone published purported company and customer information, but GMO had not confirmed a ransomware attack at that time. The notice’s times are Japan local time.
Evidence status: company-confirmed unauthorized access, with an attacker threat and a publication whose contents were still being checked. The reviewed notices do not establish widespread encryption or malware on every customer’s local PC.
A cloud incident can require local containment
The affected service provides hosted Windows desktops. The report says GMO detected the intrusion on October 20 and subsequently shut down servers to limit damage. This is a specific Desktop Cloud incident, not evidence that every GMO hosting or domain-registration customer is affected.
GMO’s October 26 account-protection notice addresses devices used to connect to Desktop Cloud, including PCs and smartphones. Its investigators were collecting volunteered customer PCs to determine whether malware, including ransomware, had actually been planted.
The October 27 morning notice asked customers to back up their data, disconnect the network, power down and unplug PC cables before the attacker’s noon deadline. The later 13:55 notice retained the isolation request after that deadline. These were precautionary instructions to this service’s customers, not a general recommendation to shut down unrelated computers.
An attacker threatening a timed payload and an investigator confirming one are different levels of evidence. A missed deadline likewise does not establish that an affected device is clean. The October 28 update below changes the earlier shutdown guidance.
Protect accounts from a separate device
GMO’s October 26 guidance specifies using a different, safe device and official sites, rather than links in email or text messages. It asks affected customers to:
- End active sessions across devices. Use the relevant provider’s account page or support channel to disconnect them.
- Change relevant passwords, including financial, email and Google accounts, and enable multifactor authentication.
- Remove unfamiliar connected apps, mail-forwarding settings, browser extensions and registered devices.
- Keep browser synchronization off until checks are complete. Otherwise account or browser changes may spread between devices.
The provider also requests full antivirus scans, rather than quick scans, and backups of important files while disconnected from the network. Follow its current recovery instructions for the affected device; a password change alone does not remove malware.
The report warns that MetaTrader credentials and trading-account details may have been exposed. It says payment information was unaffected. Those are reported scope assessments, not a complete forensic inventory.
Verify notices without visiting the alleged leak
At 12:30 on October 27, GMO says it observed someone publishing information claimed to concern the company and its customers. Its 13:55 notice says verification was ongoing and some material could be inaccurate. It promises individual notification when it confirms a customer’s information is present.
GMO’s 14:55 follow-up warns against sharing alleged leaked records and against incident-related phishing. The company says it will never ask for passwords or authentication codes. It also warns against requests for fees to recover losses.
Use the company’s independently opened incident pages and known support channel. Treat an unexpected compensation or recovery message as something to verify, even if it contains accurate personal information.
Caveat: The intrusion path, extent of local-device infection and complete exposed-data inventory remain unresolved in the reviewed notices. GMO is the affected provider and supplies the investigation’s current assessment.
Update: October 28, 10:46 EDT — scan and back up before reusing PCs
GMO’s fourteenth notice, issued October 28 at 18:20 Japan time, changes the operational guidance quoted above. It thanks customers for shutting down PCs and asks them to perform a security scan and obtain a backup before using them again. The earlier shutdown request should not be read as an indefinite instruction.
The company says its analysis of customer devices submitted for examination has found no evidence of malware infection or ransomware attack so far. Detailed investigation continues. That finding concerns the examined devices, not a forensic clearance of every customer’s computer or account.
Its thirteenth notice separately reports that the domain hosting purported stolen information was disabled around 04:00 Japan time on October 28. A domain takedown cannot establish that copied records were deleted or that account credentials are safe.
Continue the separate account-protection steps through official channels, and follow current provider instructions for the affected service. Neither notice confirms restoration of every hosted desktop or settles the full data-exposure question.