GMO Group Urges Customers to Shut Down PCs After Onamae Desktop Cloud Breach

GMO Group has told customers to disconnect systems from the internet and shut down computers after an attacker who breached its Onamae Desktop Cloud threatened to launch a ransomware attack.

Rows of switched-off desktop computers in an empty open-plan office in Riyadh at dusk.

Key points

  • GMO Group asked customers to disconnect systems from the internet and shut down computers.
  • The warning follows a breach of the company's Onamae Desktop Cloud service.
  • The threat actor threatened to launch a ransomware attack on the day of the report.
  • The source excerpt gives no further technical detail on the intrusion or its scope.

What was reported

GMO Group has urged its customers to disconnect their systems from the internet and shut down their computers. The request came after a threat actor who had breached the company's Onamae Desktop Cloud service threatened to launch a ransomware attack on the day of the report.

What is not yet known

The available excerpt does not describe how the intrusion happened, how many customers are affected, or what demands the attacker has made. Readers should treat the situation as developing and avoid assuming details that the provider has not confirmed.

Relevance for Saudi institutions

The case is a reminder that a compromise at a cloud or hosted desktop provider can quickly become a risk for the customers who depend on it. Institutions in the Kingdom that use hosted desktop or similar remote-access services from any provider should know how they would respond if that provider issued a comparable warning, including who can authorise isolating systems and how business operations continue meanwhile.

There is no indication in the source that Saudi organisations are affected. The practical value lies in checking readiness rather than reacting to this specific incident.

What to do now

  1. Inventory hosted desktop, remote-access and other cloud services supplied by third parties, and record the contact point for each provider.
  2. Confirm who is authorised to order emergency isolation of systems and that the procedure is documented.
  3. Check that offline, tested backups exist for systems that depend on provider-hosted services.
  4. Review incident response and business continuity plans for a scenario in which a provider warns of imminent ransomware.
  5. Ask critical providers how they will notify you of a breach and what interim guidance they give.

How useful was this story?

Need help acting on this?

Our consultants can assess your exposure and map the change to your controls and evidence.

Talk to an expert

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment